# CVE-2026-64943: Apache Answer sensitive information insertion in log files

Source: https://junglewise.ai/threats/cve-2026-64943-insertion-of-sensitive-information-into-log-file-vulnerability-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-19. Updated: 2026-10-19  
License: CC BY 4.0 with a link back

CVE-2026-64943 · Severity: info · Published 2026-10-19

Apache Answer, a community-driven Q&A platform, writes full API keys to application logs on every authenticated request. Anyone with access to read the application logs can recover these bearer credentials and use them to impersonate legitimate users or access protected resources.

Technologies: [Apache Answer](https://junglewise.ai/threats/technologies/apache-answer). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-64943 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-64943 being exploited in the wild.

**How severe is CVE-2026-64943?** Informational severity, published 19 October 2026.

**Which products and versions are affected?** Apache Answer through 2.0.2.

**Is there a fix for CVE-2026-64943?** Yes: fixed in 2.0.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-64943 attacked?** It is attacked with local access, in a web application.

**Am I affected by CVE-2026-64943?** Check whether you run Apache Answer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 2.0.3

## Technical details

The vulnerability is an insertion of sensitive information (CWE-532) where API keys are logged in plaintext on each authenticated request. An attacker with local log-file read access or access to centralized logging systems can retrieve active bearer tokens and replay them for unauthorized API access. The fix is available in version 2.0.3.

## Affected products

- Apache Answer through 2.0.2

## Timeline

- 2026-10-19: disclosed

## References

- [https://lists.apache.org/thread/gczojx5ypncn1x1pg9z1cphb54t23zzg](https://lists.apache.org/thread/gczojx5ypncn1x1pg9z1cphb54t23zzg)

## Related threats

- [Apache Answer missing authentication for reactions API](https://junglewise.ai/threats/cve-2026-90910-missing-authentication-for-critical-function-vulnerability-in)
- [Apache Answer authentication algorithm implementation flaw](https://junglewise.ai/threats/cve-2026-86589-incorrect-implementation-of-authentication-algorithm)
- [Apache Answer missing authorization checks](https://junglewise.ai/threats/cve-2026-79633-vulnerability-in-apache-answer-this-issue-affects-apache-answer)
- [Apache Answer insufficient session expiration](https://junglewise.ai/threats/cve-2026-79624-insufficient-session-expiration-vulnerability-in-apache-answer)
- [Apache Answer sensitive information exposure in search](https://junglewise.ai/threats/cve-2026-79620-exposure-of-sensitive-information-through-data-queries)