Vulnerability in apisix (CVE-2026-44087)
Summary
Vulnerability in apisix (CVE-2026-44087). Confidential information can be exposed externally. Mitigation: upgrade to 3.17.0 or later.
Original description
The description as published by the source.
Insufficient Verification of Data Authenticity vulnerability in Apache APISIX.
The openid-connect plugin under default configuration has an attack surface that allows the attacker to spoof identity headers allowing the attacker to get unauthorized access the protected resources.
This issue affects Apache APISIX: from 2.3 through 3.16.0.
Users are recommended to upgrade to version 3.17.0, which fixes the issue.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44087 has been found in apisix.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade apisix to 3.17.0 or later.
If unsure, ask your IT team or search "apisix CVE-2026-44087" on the vendor's site.
CVE-2026-44087 (apisix) — CWE-345 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.17.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-345) exists in apisix.
Check the vendor advisory for the affected versions of apisix.
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.
Update to 3.17.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'apisix' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'apisix' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
apisixを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade apisix to 3.17.0ステージング環境で 3.17.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory lists.apache.org
- advisory openwall.com
- web nvd.nist.gov
- web github.com