Skip to main content

Apache APISIX CVE-2025-62232

HIGH
Insertion of Sensitive Information into Log File (CWE-532)
2025-10-31 security@apache.org
7.5
CVSS 3.1 · Vendor: apache
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain read access to error logs or log sink
  2. Exploit
    Locate basic-auth INFO/DEBUG entries
  3. Execution
    Extract plaintext username and password
  4. Impact
    Replay credentials against protected APIs

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A09:2025 - Security Logging & Alerting Failures
ASVS 5.0
V16 - Security Logging and Error Handling Log data sanitization
Exploitation Conditions

Exploitation requires the APISIX log level to be configured to INFO or DEBUG (not the default WARN) AND the basic-auth plugin to be in use; under these conditions plaintext credentials are written to error logs and forwarded to any configured log sinks. The attacker must then have read access to those error logs or downstream log aggregation systems to harvest the credentials - the flaw does not itself grant log access. Limiting factors: default (non-verbose) logging configurations are not affected, and successful credential theft depends on pre-existing access to the log storage or sink, meaning this is primarily an insider / post-compromise / supply-chain-of-logs risk rather than direct remote exploitation against default configurations.

Impact

This is a CWE-532 credential-in-logs disclosure in the Apache APISIX basic-auth plugin, scored CVSS 7.5 (C:H/I:N/A:N) with no public exploit identified at time of analysis (no POC, not in CISA KEV, no EPSS score supplied). The headline signal to scrutinize is the CVSS vector: AV:N/AC:L/PR:N/UI:N portrays a trivially remote, unauthenticated, default-configuration flaw, but the description contradicts this - exploitation is contingent on (1) the log level being set to INFO or DEBUG, which is NOT the default (APISIX defaults to WARN), and (2) an actor already having read access to the error logs or downstream log sinks (SIEM, log aggregator, file system). Those are the real preconditions, so the practical attack surface is far narrower than AV:N/PR:N suggests - this is better characterized as a local/configuration-dependent information exposure than a remotely exploitable one. The impact is nonetheless serious where conditions are met: plaintext usernames and passwords flowing into log pipelines widely multiplies who can harvest them and enables lateral movement. Net assessment: a genuine credential-hygiene priority for operators running verbose logging, but NOT a drive-by network-exploitable critical issue; the CVSS 7.5 overstates real-world remote risk for default deployments. Conflict to verify: CVSS claims network vector with no privileges, yet the described attack requires non-default verbose logging plus log-access - verify intended attack model with Apache.

Exploit ScenarioDerived

An operator runs APISIX with log level set to INFO or DEBUG; every basic-auth request causes the plugin to write the plaintext username and password into the error log, which is forwarded to a centralized log sink. An insider, a compromised logging/monitoring account, or anyone with read access to the aggregated logs then harvests these credentials and replays them against protected upstream APIs. No public exploit code is required - the credentials are simply present in readable logs.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 07, 2026

Plaintext credential exposure in Apache APISIX before 3.14 affects deployments using the basic-auth plugin with INFO or DEBUG logging enabled, allowing anyone who can read the error logs or downstream log sinks to obtain usernames and passwords. The vendor-published CVSS is 7.5, but the independent assessment rates this as AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N because exploitation requires non-default verbose logging, basic-auth use, and pre-existing access to logs or log sinks; no public exploit identified at time of analysis, not in CISA KEV, and no EPSS score supplied.

RemediationAI

Upgrade to Apache APISIX 3.14, the vendor-released patch that fixes the credential logging issue via PR 12629; see the advisory at https://lists.apache.org/thread/32hdgh570btfhg02hfc7p7ckf9v83259. If immediate upgrade is not possible, set the APISIX log level to WARN or higher and never run the basic-auth plugin with INFO or DEBUG logging, accepting reduced diagnostic detail as a trade-off. Restrict read access to APISIX error logs, rotated log files, and all downstream log sinks or aggregators to trusted operators; this limits exposure but does not fix the underlying logging flaw. If logs may already have been exposed, rotate all basic-auth credentials and audit log access; log redaction or filtering at the sink can help but must be verified against username and password fields and can be bypassed by log format changes. Additional context is available at http://www.openwall.com/lists/oss-security/2025/10/30/4.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Apache APISIX is an API gateway that processes HTTP traffic through plugins, including basic-auth for credential verification. The flaw is CWE-532 (Insertion of Sensitive Information into Log File): when the APISIX log level is configured to INFO or DEBUG rather than the default WARN, the basic-auth plugin writes plaintext usernames and passwords into error logs, and those logs may be forwarded to downstream log sinks or aggregators. The CPE cpe:2.3:a:apache:apisix:*:*:*:*:*:*:*:* identifies the affected APISIX family before the fix. The published CVSS:3.1/AV:N/AC:L/PR:N/UI:N vector overstates practical exploitability relative to the assessed CVSS:3.1/AV:L/AC:H/PR:L/UI:N vector, because an attacker must already have read access to the logs or log storage; the bug does not grant log access or bypass authentication by itself.

Know when Apisix gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (apache) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 4.7 MEDIUM

Requires non-default INFO/DEBUG logging (AC:H) and read access to logs/sinks (AV:L, PR:L); only credential confidentiality is impacted, so I:N and A:N.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (apache).

CVSS VectorVendor: apache

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

DescriptionCVE.org

Sensitive data exposure via logging in basic-auth leads to plaintext usernames and passwords written to error logs and forwarded to log sinks when log level is INFO/DEBUG. This creates a high risk of credential compromise through log access. It has been fixed in the following commit:  https://github.com/apache/apisix/pull/12629 Users are recommended to upgrade to version 3.14, which fixes this issue.

Executive ViewAI

Why It Matters

Apache APISIX deployments that use the basic-auth plugin with INFO or DEBUG logging enabled can expose plaintext API credentials to anyone with access to log files or downstream log sinks. This credential exposure could enable unauthorized access to APIs and backend services, potentially leading to data breaches, compliance violations, and loss of customer trust. Leadership should prioritize remediation because API gateway credentials often provide broad access to internal systems.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.5%
Top 61% exploitable
Prevalence
Medium
popular open-source API gateway, common but not universally deployed
Data Quality
2 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Affected Products (CPE)CVE.org

cpe:2.3:a:apache:apisix:*:*:*:*:*:*:*:*

More in Apisix

View all
CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2020-13945 MEDIUM POC
6.5 Dec 07

In Apache APISIX, the user enabled the Admin API and deleted the Admin API access IP restriction rules. Rated medium sev

CVE-2021-43557 HIGH POC
7.5 Nov 22

The uri-block plugin in Apache APISIX before 2.10.2 uses $request_uri without verification. Rated high severity (CVSS 7.

CVE-2022-25757 CRITICAL
9.8 Mar 28

In Apache APISIX before 2.13.0, when decoding JSON with duplicate keys, lua-cjson will choose the last occurred value as

CVE-2026-75005 HIGH
8.7 Aug 26

CPU exhaustion via algorithmic complexity in Apache APISIX 3.17.0 allows unauthenticated remote attackers to pin a gatew

CVE-2025-27446 HIGH
7.8 Jul 06

Incorrect Permission Assignment for Critical Resource vulnerability in Apache APISIX(java-plugin-runner). Local listeni

CVE-2022-29266 HIGH
7.5 Apr 20

In APache APISIX before 3.13.1, the jwt-auth plugin has a security issue that leaks the user's secret key because the er

CVE-2026-75020 HIGH
7.0 Aug 26

LDAP injection in Apache APISIX's ldap-auth plugin allows a caller holding valid credentials for any LDAP directory entr

CVE-2026-74848 HIGH
7.0 Aug 26

Response poisoning in Apache APISIX 2.12.0 through 3.17.0 enables remote attackers to manipulate the gateway's serverles

CVE-2024-32638 MEDIUM
6.3 May 02

Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') vulnerability in Apache APISIX when using `forwa

CVE-2026-63041 MEDIUM
5.3 Aug 26

Authorization bypass and privilege escalation in Apache APISIX 3.11.0-3.17.0 stem from the `attach-consumer-label` plugi

CVE-2025-46647 MEDIUM
5.3 Jul 02

CVE-2025-46647 is a security vulnerability (CVSS 5.3). Remediation should follow standard vulnerability management proce

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy