dbcve.org
ApisixApplication · Apache

CVE-2026-47341

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-19
Fix available
A fix is available. Upgrade to 3.17.0 or later.
See remediation →
74/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
Authentication Bypass by Capture-replay vulnerability in Apache APISIX. Attacker can benefit from certain configurations in hmac-auth to re-use a token forever, bypassing expiry. This issue affects Apache APISIX: from 3.11.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 · high confidence

The hmac-auth plugin in Apache APISIX versions 3.11.0-3.16.0 contains a capture-replay vulnerability that allows attackers to replay captured authentication tokens, bypassing expiry checks and enabling indefinite token reuse.

MitigationUpgrade Apache APISIX to version 3.17.0 or later to obtain the security patch for the hmac-auth plugin 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:>= 3.11.0, < 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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Apache APISIX installation version
    Run `apisix version` or inspect the version file in the APISIX installation directory to determine the exact version number
    Affected if The installed version is 3.11.0, 3.11.1, 3.11.2, 3.12.0, 3.12.1, 3.13.0, 3.13.1, 3.14.0, 3.14.1, 3.15.0, 3.15.1, or 3.16.0 (any version >= 3.11.0 and < 3.17.0)
  2. Verify hmac-auth plugin is enabled
    Inspect the Apache APISIX configuration file (config.yaml) or check the enabled plugins via the APISIX admin API endpoint `/apisix/admin/plugins` to confirm hmac-auth is listed among enabled plugins
    Affected if The hmac-auth plugin appears in the enabled plugins list in the APISIX configuration or admin API response
  3. Check for hmac-auth consumer configuration
    Query the APISIX admin API at `/apisix/admin/consumers` or inspect the consumer configuration file to identify consumers using the hmac-auth authentication method
    Affected if There exists a consumer configured with the hmac-auth plugin (plugin name: `hmac-auth` in the consumer configuration)
  4. Inspect hmac-auth replay protection settings
    Review the hmac-auth plugin configuration for any nonce, timestamp validation, or replay protection parameters. Check if `validate_timestamp` or similar replay-prevention settings are properly configured and enforced
    Affected if The hmac-auth plugin lacks proper timestamp/nonce validation or replay protection, allowing the same signed request to be reused

You are affected if Apache APISIX version is 3.11.0 or higher but below 3.17.0 AND the hmac-auth plugin is enabled and configured for consumer authentication

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 security patch for the hmac-auth plugin vulnerability.

Recommended fix High confidence

3.17.0

  1. 1. Back up your current Apache APISIX configuration files (apisix.yaml, config.yaml) and any custom plugin configurations.
  2. 2. Review the Apache APISIX 3.17.0 release notes for any migration requirements or breaking changes specific to your configuration.
  3. 3. Stop the Apache APISIX service to prevent requests during upgrade.
  4. 4. Upgrade Apache APISIX to version 3.17.0 using your installation method (e.g., package manager, Docker image, or source compilation).
  5. 5. Restore your configuration files from the backup if needed.
  6. 6. Start the Apache APISIX service and verify it is running correctly.
  7. 7. Test the hmac-auth plugin functionality to confirm authentication is working as expected, including token expiry enforcement.
Caveat Review 3.17.0 release notes for any plugin or configuration changes that may affect your setup

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

Fix this in Apisix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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