dbcve.org
ApisixApplication · Apache

CVE-2026-31924

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 3.16.0 or later.
See remediation →
62/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
Cleartext Transmission of Sensitive Information vulnerability in Apache APISIX. tencent-cloud-cls log export uses plaintext HTTP This issue affects Apache APISIX: from 2.99.0 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

Cleartext transmission vulnerability in Apache APISIX where the tencent-cloud-cls log export feature sends sensitive log data over plaintext HTTP instead of encrypted HTTPS, allowing potential interception of sensitive information.

MitigationUpgrade to Apache APISIX version 3.16.0 or later to resolve the plaintext HTTP transmission issue, or temporarily disable the tencent-cloud-cls log export plugin until upgrade is possible.

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.99.0, < 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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 command: apisix version or check package manager (rpm -q apisix, dpkg -l apisix)
    Affected if Installed version is >= 2.99.0 and < 3.16.0
  2. Locate tencent-cloud-cls plugin configuration
    Check for conf/plugins/tencent-cloud-cls.lua in APISIX config directory, or search for 'tencent-cloud-cls' in /etc/apisix/conf/ directory
    Affected if Plugin configuration file exists or references tencent-cloud-cls
  3. Inspect plugin endpoint configuration
    Examine the tencent-cloud-cls configuration for log_endpoint parameter; check if value uses HTTP:// instead of HTTPS://
    Affected if Configuration specifies HTTP endpoint (not HTTPS) for log transmission
  4. Verify plugin is actively enabled
    Check apisix.yaml or config.yaml for tencent-cloud-cls in enabled_plugins list, or inspect running plugin list via APISIX admin API
    Affected if tencent-cloud-cls plugin appears in enabled_plugins list

User is affected if running APISIX version 2.99.0 through 3.15.x with the tencent-cloud-cls plugin enabled and configured to use plaintext HTTP endpoint for log export.

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 version 3.16.0 or later to resolve the plaintext HTTP transmission issue, or temporarily disable the tencent-cloud-cls log export plugin until upgrade is possible.

Recommended fix High confidence

3.16.0

  1. 1. Identify current Apache APISIX version by checking the version file or running:apisix version
  2. 2. Create a full backup of the APISIX configuration directory (typically /usr/local/apisix/conf or /etc/apisix)
  3. 3. Create a backup of any custom plugins or modified files
  4. 4. Stop the Apache APISIX service: apisix stop or systemctl stop apisix
  5. 5. Upgrade Apache APISIX to version 3.16.0 using the appropriate package manager or installation method (e.g., yum update apisix, apt-get install apisix, or tarball installation)
  6. 6. Verify the new version is installed: apisix version (should show 3.16.0)
  7. 7. Restore any custom configurations from the backup
  8. 8. Start the Apache APISIX service: apisix start or systemctl start apisix
Caveat Review the Apache APISIX 3.16.0 release notes for any breaking changes; minor version upgrades typically have minimal impact but custom plugins or configurations may need adjustment

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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