Description
Insertion of Sensitive Information into Log File vulnerability in Apache Answer.



This issue affects Apache Answer: through 2.0.2.

Full API keys are written to application logs on every authenticated request, allowing anyone with log-read access to recover and replay active bearer credentials.


Users are recommended to upgrade to version 2.0.3, which fixes the issue.
Published: 2026-10-19
Score: n/a
EPSS: n/a
KEV: No
Impact: API keys are logged in plaintext, allowing credential compromise
Action: Immediate Patch
AI Analysis

Impact

Apache Answer writes the complete API key to the application log on every authenticated request. The logged credential can be recovered by anyone who has read access to the logs, enabling replay of the bearer token and full impersonation of the legitimate user. This flaw is an example of inserting sensitive information into an unencrypted log file (CWE-532).

Affected Systems

The vulnerability affects all releases of Apache Answer up through version 2.0.2 published by the Apache Software Foundation. Users of those versions should verify their deployment and plan to upgrade to the patched release, 2.0.3, which removes the logging of credentials.

Risk and Exploitability

The flaw provides an information disclosure that is highly valuable to an attacker who can read the logs. It does not allow arbitrary code execution or remote privilege escalation, but it does enable credential replay. Because the vulnerability is tied to log file access, the exploitation risk is moderate to high depending on the security of the log environment. No exploit code has been published, and the vulnerability is not listed in CISA KEV. The EPSS score is not available. The patch removes the logging behavior, eliminating the risk.

Generated by OpenCVE AI on October 19, 2026 at 10:22 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Apache Answer to version 2.0.3 or later to stop logging API keys
  • Configure log file permissions so that only privileged system accounts can read log files
  • Audit any log aggregation or monitoring services to ensure they do not have unrestricted access to the application logs

Generated by OpenCVE AI on October 19, 2026 at 10:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 19 Oct 2026 09:45:00 +0000

Type Values Removed Values Added
Description Insertion of Sensitive Information into Log File vulnerability in Apache Answer. This issue affects Apache Answer: through 2.0.2. Full API keys are written to application logs on every authenticated request, allowing anyone with log-read access to recover and replay active bearer credentials. Users are recommended to upgrade to version 2.0.3, which fixes the issue.
Title Apache Answer: API keys logged in plaintext during authentication
Weaknesses CWE-532
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-10-19T10:13:38.626Z

Reserved: 2026-07-21T04:36:17.326Z

Link: CVE-2026-64943

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-19T10:16:48.047

Modified: 2026-10-19T10:16:48.047

Link: CVE-2026-64943

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-19T10:30:13Z

Weaknesses
  • CWE-532

    Insertion of Sensitive Information into Log File