dbcve.org
ApisixApplication · Apache

CVE-2026-44046

MEDIUM · 5.8 CVSS v3.1 Published 2026-06-19
Fix available
A fix is available. Upgrade to 3.17.0 or later.
See remediation →
67/100
Remediation priority · Elevated
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
Use of Less Trusted Source vulnerability in Apache APISIX. Attacker can take advantage of wolf-rbac plugin under default configuration to potentially pollute logs with spoofed identity information and exploit IP based access control rules. This issue affects Apache APISIX: from 1.2.0 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 wolf-rbac plugin in Apache APISIX uses a less trusted source (likely client-supplied HTTP headers) for identity and RBAC decisions instead of a more trusted internal source. In the default configuration, attackers can manipulate these headers to spoof identity information in logs and bypass IP-based access control rules.

MitigationUpgrade Apache APISIX to version 3.17.0 or later, which contains the fixed wolf-rbac plugin. Alternatively, if upgrading is not immediately possible, reconfigure the plugin to use trusted internal sources for identity verification rather than client-supplied headers.

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:>= 1.2, < 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
Changed
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/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. Check installed Apache APISIX version
    Run `apisix version` or check the version from your package manager or deployment manifests
    Affected if The installed version is >= 1.2 and < 3.17.0
  2. Verify wolf-rbac plugin is enabled
    Check the APISIX configuration file (apisix.yaml or config.yaml) for wolf-rbac in the plugins list, or query the APISIX admin API endpoint `/apisix/admin/plugins`
    Affected if The wolf-rbac plugin appears in the enabled plugins list
  3. Inspect wolf-rbac plugin configuration
    Query the APISIX admin API at `/apisix/admin/plugins/wolf-rbac` or check the route/consumer configuration where wolf-rbac is applied
    Affected if The plugin is configured and uses client-supplied HTTP headers (such as X-User-Id, X-Username, or similar headers) for identity verification rather than internal trusted sources
  4. Check for IP restriction bypass exposure
    Review routes protected by wolf-rbac that also use IP restriction, and verify whether the plugin configuration trusts client-provided headers for IP validation
    Affected if Routes combine wolf-rbac with IP-based access control and the plugin is configured to read identity from client headers

You are affected if Apache APISIX version is between 1.2 and 3.16.x inclusive AND the wolf-rbac plugin is enabled using default configuration that relies on client-supplied HTTP headers for identity decisions.

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, which contains the fixed wolf-rbac plugin. Alternatively, if upgrading is not immediately possible, reconfigure the plugin to use trusted internal sources for identity verification rather than client-supplied headers.

Recommended fix High confidence

3.17.0

  1. 1. Backup your current Apache APISIX configuration directory (typically /usr/local/apisix/conf or /etc/apisix)
  2. 2. Backup any custom plugins or modified files
  3. 3. Stop the Apache APISIX service
  4. 4. Upgrade Apache APISIX to version 3.17.0 using your installation method (e.g., RPM package, Docker image, or source compilation)
  5. 5. Restore your configuration from the backup
  6. 6. Verify the wolf-rbac plugin configuration and ensure default settings are reviewed
  7. 7. Start the Apache APISIX service
  8. 8. Verify the upgrade was successful and the wolf-rbac plugin functions correctly
Caveat Review release notes for 3.17.0 for any breaking changes; minor version upgrades typically have minimal compatibility impact

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

Fix this in Apisix Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44046 — 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-44046 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