How severe is CVE-2025-27371?

CVE-2025-27371 has a CVSS 3.x base score of 6.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is low, integrity high, and availability none.

Is CVE-2025-27371 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-27371?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-27371 have an EU (EUVD) identifier?

Yes. CVE-2025-27371 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-5567.

When was CVE-2025-27371 published?

CVE-2025-27371 was published on 2025-03-03 and last updated on 2026-06-17.

CVE-2025-27371

CVE-2025-27371 is a medium-severity vulnerability with a CVSS 3.x base score of 6.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-305.

Key facts

Severity: Medium (CVSS 3.x base score 6.9)
EPSS exploit prediction: 0% (24th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-5567
Weakness: CWE-305
Published: 2025-03-03
Last modified: 2026-06-17

Description

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).

Frequently asked questions

What is CVE-2025-27371?: 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).
How severe is CVE-2025-27371?: CVE-2025-27371 has a CVSS 3.x base score of 6.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is low, integrity high, and availability none.
Is CVE-2025-27371 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-27371?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-27371 have an EU (EUVD) identifier?: Yes. CVE-2025-27371 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-5567.
When was CVE-2025-27371 published?: CVE-2025-27371 was published on 2025-03-03 and last updated on 2026-06-17.

References

Other CWE-305 vulnerabilities

CVE-2025-4320 — Critical (CVSS 10.0): Authentication Bypass by Primary Weakness, Weak Password Recovery Mechanism for Forgotten Password vulnerability in…
CVE-2025-24522 — Critical (CVSS 10.0): KUNBUS Revolution Pi OS Bookworm 01/2025 is vulnerable because authentication is not configured by default for the…
CVE-2024-36388 — Critical (CVSS 10.0): MileSight DeviceHub - CWE-305 Missing Authentication for Critical Function
CVE-2024-1403 — Critical (CVSS 10.0): In OpenEdge Authentication Gateway and AdminServer prior to 11.7.19, 12.2.14, 12.8.1 on all platforms supported by the…
CVE-2026-25555 — Critical (CVSS 9.8): OpenBullet2 through version 0.3.2 contains an authentication bypass vulnerability in the API key authentication…
CVE-2026-4670 — Critical (CVSS 9.8): Authentication bypass by primary weakness vulnerability in Progress Software MOVEit Automation allows Authentication…

Browse all CWE-305 vulnerabilities →