CVE-2025-27371: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-rh3q-7g79-rp3x
CVSS 6.9
CWE-305 CWE-863
Published
Advisory Summary

CVE-2025-27371 is a MODERATE (CVSS 6.9) security vulnerability vulnerability (CWE-305: Authentication Bypass by Primary Weakness) affecting Software libraries in the Maven ecosystem. The weakness occurs when the authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error.. Remediation is available in the latest vendor maintenance releases.

CVE-2025-27371 at a Glance

CVE Identifier CVE-2025-27371
GHSA Identifier GHSA-rh3q-7g79-rp3x
Severity MODERATE
CVSS v3.1 Base Score 6.9
CWE Classification CWE-305: Authentication Bypass by Primary Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 6.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2025-27371

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2025-27371, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-305: Authentication Bypass by Primary Weakness, where the authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

References

Frequently Asked Questions

What is CVE-2025-27371?
CVE-2025-27371 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-305: Authentication Bypass by Primary Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2025-27371?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2025-27371?
CVE-2025-27371 has a CVSS v3.1 base score of 6.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N.
What CWE is associated with CVE-2025-27371?
CVE-2025-27371 is classified under CWE-305: Authentication Bypass by Primary Weakness (The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error.).
How can I check Maven dependencies for CVE-2025-27371?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rh3q-7g79-rp3x",
  "modified" : "2025-04-25T15:31:20Z",
  "published" : "2025-03-03T18:31:30Z",
  "aliases" : [ "CVE-2025-27371" ],
  "details" : "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).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-27371"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/OWASP/ASVS/issues/2678"
  }, {
    "type" : "WEB",
    "url" : "https://eprint.iacr.org/2025/629"
  }, {
    "type" : "WEB",
    "url" : "https://openid.net/notice-of-a-security-vulnerability"
  }, {
    "type" : "WEB",
    "url" : "https://openid.net/wp-content/uploads/2025/01/OIDF-Responsible-Disclosure-Notice-on-Security-Vulnerability-for-private_key_jwt.pdf"
  }, {
    "type" : "WEB",
    "url" : "https://talks.secworkshop.events/osw2025/talk/R8D9BS"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-305", "CWE-863" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2025-03-03T18:15:40Z"
  }
}