CVE-2025-27371

6.9 MEDIUM 0.3% exploit odds No fix listed Other

What it is

In certain IETF OAuth 2.0-related specifications, when the JSON Web Token Profile for OAuth 2.0 Client Authentication mechanism is used, there are ambiguities in the audience values of JWTs sent to authorization servers. The affected RFCs may include RFC 7523, and also RFC 7521, RFC 7522, RFC 9101 (JAR), and RFC 9126 (PAR).

At a glance

Exploitability: Can be exploited over the network without logging in, but needs a user to act. High risk of data tampering.
Exploit odds: 0.3% chance of exploitation in the next 30 days (EPSS).
Fix: No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

2025-03-03 18:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-06-17 09:03 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 0.3% in the next 30 days (EPSS).
Severity: 6.9 MEDIUM (CVSS).
Fix: none linked yet, which raises it.

Details

Published: 2025-03-03 18:15 UTC
Last modified: 2026-06-17 09:03 UTC
Exploit probability: 0.3% · EPSS, next 30 days
Weakness: CWE-305
Record status: Deferred

Attack profile CVSS 3.1 · 6.9

Attack vector: Network
Complexity: High
Privileges needed: None
User interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: High
Availability: None

Raw vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2025-27371.md and follow it. Check whether this project is affected by CVE-2025-27371. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

References

NVD record · CVE.org record