Credential disclosure via plaintext API-key logging
Published Oct 19, 2026 · Updated Oct 19, 2026
Credential disclosure in Apache Answer 2.0.2 and earlier allows attackers to recover API keys from authentication logs. Authentication request logging writes full API keys to application logs on every authenticated request instead of withholding the credentials. Exploitation requires log-read access and exposes active bearer credentials for replay with the access granted to those keys.
Summary
What happened
Credential disclosure in Apache Answer 2.0.2 and earlier allows attackers to recover API keys from authentication logs. Authentication request logging writes full API keys to application logs on every authenticated request instead of withholding the credentials. Exploitation requires log-read access and exposes active bearer credentials for replay with the access granted to those keys.
The record
- CVE
- CVE-2026-64943
- Published
- Oct 19, 2026
- Updated
- Oct 19, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Answer
- Classifications
- CWE-532, T1552
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 19, 2026CVE publishedPublication date reported by the CVE source.
- Oct 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started