dbcve.org
ApisixApplication · Apache

CVE-2026-31923

HIGH · 7.5 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 3.16.0 or later.
See remediation →
84/100
Remediation priority · High
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
Cleartext Transmission of Sensitive Information vulnerability in Apache APISIX. This can occur due to `ssl_verify` in openid-connect plugin configuration being set to false by default. This issue affects Apache APISIX: from 0.7 through 3.15.0. Users are recommended to upgrade to version 3.16.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 openid-connect plugin in Apache APISIX has SSL/TLS certificate verification disabled by default (ssl_verify: false). This allows man-in-the-middle attackers to intercept sensitive OpenID Connect authentication tokens and potentially steal user credentials during the authentication flow.

MitigationUpgrade to Apache APISIX 3.16.0 or set ssl_verify: true in the openid-connect plugin configuration to enforce certificate validation.

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:>= 0.7, < 3.16.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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify Apache APISIX version
    Run `apisix version` or check the version in your deployment/package manager to determine if version is >= 0.7 and < 3.16.0
    Affected if Installed version falls within >= 0.7 and < 3.16.0 range
  2. Locate openid-connect plugin configuration
    Search for openid-connect or oidc plugin configuration files in your APISIX config directory, typically in the `conf/plugins/` directory or within route/service configurations that reference the openid-connect plugin
    Affected if The openid-connect plugin is configured and in use
  3. Inspect ssl_verify setting
    Examine the openid-connect plugin configuration block and look for the `ssl_verify` parameter. Check whether it is explicitly set to `true` or if it is absent (defaulting to `false`)
    Affected if ssl_verify is absent from configuration or explicitly set to false

You are affected if APISIX version is between 0.7 and 3.16.0 (exclusive), the openid-connect plugin is in use, and ssl_verify is not set to true in the plugin configuration.

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.16.0 or later
Fixed in 3.16.0
Interim mitigation

Upgrade to Apache APISIX 3.16.0 or set ssl_verify: true in the openid-connect plugin configuration to enforce certificate validation.

Recommended fix High confidence

3.16.0

  1. 1. Backup your current Apache APISIX configuration files (e.g., config.yaml, plugins configuration) and any custom plugin code
  2. 2. Review the Apache APISIX 3.16.0 release notes and changelog for any breaking changes relevant to your setup
  3. 3. Upgrade Apache APISIX to version 3.16.0 using your package manager or build process (e.g., `yum upgrade apisix` or `apt-get upgrade apisix`, or rebuild from source)
  4. 4. After upgrade, verify the openid-connect plugin configuration to ensure `ssl_verify` is properly set (recommended: `ssl_verify: true`)
  5. 5. Restart the APISIX service to apply changes
  6. 6. Test authentication flows with the openid-connect plugin in a non-production environment
  7. 7. Deploy the updated version to production
Caveat Review 3.16.0 changelog for minor breaking changes across versions; upgrade path from 0.7+ may have accumulated changes

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

Fix this in Apisix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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