# 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, the


- **Severity:** Medium 6.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Mar 2025
- **Updated:** 25 Apr 2025
- **Also known as:** GHSA-rh3q-7g79-rp3x

## What is CVE-2025-27371?

CVE-2025-27371 is a medium-severity vulnerability in IETF RFC 7523, published on 3 Mar 2025. 

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

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

## Which versions are affected by CVE-2025-27371?


## How do I fix CVE-2025-27371?

No fix has been published for CVE-2025-27371 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-27371 being exploited?

There is no known exploitation of CVE-2025-27371 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27371 and fix it if it is affected.

What it is: CVE-2025-27371 is a medium-severity vulnerability in IETF RFC 7523, published on 3 Mar 2025. 
Exploitation: There is no known exploitation of CVE-2025-27371 in the wild and no public exploit code.

Affected product: IETF RFC 7523. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-27371/ (Markdown: https://insights.sbomify.com/CVE-2025-27371/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27371
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27371
- OSV: https://osv.dev/vulnerability/CVE-2025-27371

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-27371/
Summaries are generated and may contain mistakes; the official description above is the record.