dbcve.org
ApisixApplication · Apache

CVE-2025-46647

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-02
Fix available
A fix is available. Upgrade to 3.12.0 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability of plugin openid-connect in Apache APISIX. This vulnerability will only have an impact if all of the following conditions are met: 1. Use the openid-connect plugin with introspection mode 2. The auth service connected to openid-connect provides services to multiple issuers 3. Multiple issuers share the same private key and relies only on the issuer being different If affected by this vulnerability, it would allow an attacker with a valid account on one of the issuers to log into the other issuer. This issue affects Apache APISIX: until 3.12.0. Users are recommended to upgrade to version 3.12.0 or higher.

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 openid-connect plugin in Apache APISIX fails to properly validate issuer identity during token introspection when multiple issuers share the same private key. An attacker with a valid token from one issuer can authenticate as themselves on a different issuer that shares the same key, because the plugin relies solely on the issuer claim rather than validating key-issuer binding.

MitigationUpgrade Apache APISIX to version 3.12.0 or higher, or ensure different issuers use distinct private keys rather than relying solely on issuer identification.

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.12.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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/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 version
    Run 'apisix version' or check the version in your deployment manifests/packaging
    Affected if Version is below 3.12.0
  2. Verify openid-connect plugin is enabled
    List enabled plugins via APISIX admin API at /apisix/admin/plugins or inspect your plugin configuration files
    Affected if The openid-connect plugin is present and configured for route or global proxy
  3. Identify configured issuers in openid-connect plugin
    Examine the plugin configuration (typically in route.yaml, upstreams.yaml, or apisix.yaml) for 'issuer', 'public_key', 'token_signing_alg', or related OIDC fields. Query the /apisix/admin/plugins/list endpoint if available
    Affected if Multiple 'issuer' entries or multiple endpoints pointing to different issuers share the same 'public_key' or 'jwt_secret' value
  4. Inspect key sharing across issuers
    Compare the public_key, jwt_secret, or token_signing_alg_values configuration across all configured issuers in your openid-connect setup
    Affected if Different issuers are configured with identical public_key or jwt_secret values without additional key-issuer binding validation
  5. Confirm token introspection validation logic
    Review the openid-connect plugin's 'introspection' and 'authorization_endpoint' settings in your configuration. Check if 'ssl_verify' is enabled and if 'issuer' is the sole identifier without key binding verification
    Affected if Plugin relies only on 'issuer' claim match without validating that the token's signing key belongs to that specific issuer

You are affected if running APISIX below 3.12.0 with the openid-connect plugin configured and multiple issuers share the same signing key without key-issuer binding validation.

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.12.0 or later
Fixed in 3.12.0
Interim mitigation

Upgrade Apache APISIX to version 3.12.0 or higher, or ensure different issuers use distinct private keys rather than relying solely on issuer identification.

Recommended fix High confidence

3.12.0

  1. 1. Backup your current Apache APISIX configuration and data directory
  2. 2. Check your current Apache APISIX version using `apisix version` or checking your deployment manifests
  3. 3. For package-based installations: update your package repository and run `apt-get update && apt-get install apisix` or `yum update apisix` depending on your OS
  4. 4. For Docker-based installations: update your image tag to `apisix:3.12.0` or higher in your Docker Compose/Kubernetes manifests and recreate containers
  5. 5. For source-based installations: clone the Apache APISIX repository, checkout tag `3.12.0`, and rebuild using `./apisix release`
  6. 6. After upgrade, verify the openid-connect plugin configuration: ensure introspection mode is properly configured with issuer validation
  7. 7. Test authentication flow to confirm the vulnerability is remediated
  8. 8. Monitor logs for any errors post-upgrade
Caveat Review Apache APISIX 3.12.0 release notes for any plugin or configuration changes that may affect your deployment

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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