dbcve.org
ApisixApplication · Apache

CVE-2026-44087

CRITICAL · 9.1 CVSS v3.1 Published 2026-06-19
Fix available
A fix is available. Upgrade to 3.17.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Apache APISIX openid-connect plugin has an Insufficient Verification of Data Authenticity vulnerability in its default configuration. Attackers can spoof identity headers passed through the plugin to impersonate legitimate users and gain unauthorized access to protected backend resources.

MitigationUpgrade Apache APISIX to version 3.17.0 or later to obtain the fix for this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ApisixApplication
Affected:>= 2.3, < 3.17.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache APISIX version
    Run `apisix version` or check the version in the Apache APISIX startup logs. Alternatively, inspect the version in the installed package (e.g., `rpm -q apisix` or `dpkg -l apisix`).
    Affected if The installed version is >= 2.3.0 and < 3.17.0
  2. Locate openid-connect plugin configuration
    Search for openid-connect configuration in APISIX routes, services, or global rules. Check YAML configuration files in the conf/ directory or query the APISIX Admin API endpoint `/apisix/admin/plugins` to list enabled plugins.
    Affected if The openid-connect plugin is configured and enabled in any route, service, or consumer.
  3. Inspect openid-connect plugin settings
    Review the openid-connect plugin configuration for the `trusted_full_request_headers` or `userinfo_header` settings. These headers should be explicitly defined to verify authenticity. Check configuration files or query the Admin API for plugin details.
    Affected if The plugin uses default configuration without explicitly configured trusted headers for request validation, allowing header spoofing.

You are affected if Apache APISIX version is between 2.3.0 and 3.16.x inclusive AND the openid-connect plugin is enabled with default or insufficient header verification settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.17.0 or later
Fixed in 3.17.0
Interim mitigation

Upgrade Apache APISIX to version 3.17.0 or later to obtain the fix for this vulnerability.

Recommended fix High confidence

3.17.0

  1. 1. Backup your current Apache APISIX configuration and data directory (typically located at /usr/local/apisix/conf and /usr/local/apisix/data)
  2. 2. Stop the running Apache APISIX service
  3. 3. Upgrade Apache APISIX to version 3.17.0 using your installation method (e.g., yum install apisix-3.17.0, Docker, or source compilation)
  4. 4. Verify the openid-connect plugin configuration matches your intended settings after upgrade
  5. 5. Start the Apache APISIX service
  6. 6. Test that the openid-connect plugin functions correctly with the upgrade
Caveat Review Apache APISIX 3.17.0 release notes for any breaking changes between your current version and 3.17.0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Apisix Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44087 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44087 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data