CVE-2025-27371Network attack vector

Client impersonation via ambiguous JWT audience

Published Mar 3, 2025 · Updated Apr 25, 2025

Authentication bypass in IETF RFC 7523 allows remote attackers to impersonate OAuth clients through crafted authorization-server metadata. The specification permits a token-endpoint URL as the JWT audience, so a malicious authorization server can advertise an honest server's endpoint and induce a client to sign an assertion accepted there. Exploitation requires a client that uses the same signing key with at least two authorization servers and interacts with an attacker-controlled server; the assertion enables client impersonation and unauthorized access to user resources.

CVSS severity6.9
Medium
EPSS probability0.34%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authentication bypass in IETF RFC 7523 allows remote attackers to impersonate OAuth clients through crafted authorization-server metadata. The specification permits a token-endpoint URL as the JWT audience, so a malicious authorization server can advertise an honest server's endpoint and induce a client to sign an assertion accepted there. Exploitation requires a client that uses the same signing key with at least two authorization servers and interacts with an attacker-controlled server; the assertion enables client impersonation and unauthorized access to user resources.

The record

CVE
CVE-2025-27371
Published
Mar 3, 2025
Updated
Apr 25, 2025
Vendor
Internet Engineering Task Force (IETF)
Product
RFC 7523: JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants
Classifications
CWE-305
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Mar 3, 2025CVE publishedPublication date reported by the CVE source.
  2. Apr 25, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=7523

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Internet Engineering Task Force (IETF) · RFC 7523: JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grantsversion=7523

Published CVSS scores

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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-305Authentication Bypass by Primary Weakness

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo