Identity spoofing via uncleared upstream headers
Published Jun 19, 2026 · Updated Jun 19, 2026
Improper input validation in Apache APISIX 2.12.0 through 3.16.0 allows remote authenticated users to spoof upstream identities. The forward-auth plugin leaves a client-supplied header named in upstream_headers intact when the authorization service returns HTTP 200 without that header. Exploitation requires an enabled forward-auth route with a trusted upstream identity header, allowing the client value to reach the upstream application as authenticated identity data.
Summary
What happened
Improper input validation in Apache APISIX 2.12.0 through 3.16.0 allows remote authenticated users to spoof upstream identities. The forward-auth plugin leaves a client-supplied header named in upstream_headers intact when the authorization service returns HTTP 200 without that header. Exploitation requires an enabled forward-auth route with a trusted upstream identity header, allowing the client value to reach the upstream application as authenticated identity data.
The record
- CVE
- CVE-2026-39998
- Published
- Jun 19, 2026
- Updated
- Jun 19, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache APISIX
- Classifications
- CWE-20, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 19, 2026CVE publishedPublication date reported by the CVE source.
- Jun 19, 2026Record 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.
- Affected versionversion=2.12.0 <=3.16.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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