Description
Insufficient Session Expiration vulnerability in Apache Answer.

This issue affects Apache Answer: through 2.0.1.

Administrative API keys remained usable after the owning administrator was demoted or the account was marked inactive, suspended, or deleted, allowing continued access until the keys were explicitly removed.
Users are recommended to upgrade to version 2.0.2, which fixes the issue.
Published: 2026-08-05
Score: 9.1 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability allows administrative API keys to remain valid even after the account owner has been demoted, made inactive, suspended, or deleted. This failure of session expiration means that an attacker who possesses such a key can continue to perform privileged API operations, effectively bypassing account revocation controls and potentially compromising system integrity.

Affected Systems

All installations of Apache Answer version 2.0.1 or earlier are affected. Any configuration that issues or relies on administrative API keys for services will be exposed if those keys are not manually revoked when an account’s status changes.

Risk and Exploitability

Based on the description, it is inferred that an attacker could exploit a stale key by sending requests to the standard REST API, which would allow privileged operations. The CVSS score is 9.1, indicating a high severity, and the EPSS score is <1%, showing a very low probability of exploitation, yet the impact remains severe because administrators can execute any action reserved for users with elevated privileges. The lack of presence in the CISA KEV catalog does not diminish the risk; exploitation would require possession of a stale key, which is possible if an attacker gains network access to the API endpoint.

Generated by OpenCVE AI on August 12, 2026 at 00:01 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Apache Answer to version 2.0.2 or later, which removes the lingering API key issue, via the official vendor update process.
  • Explicitly revoke all administrative API keys that are no longer associated with active administrators, using the web interface or the dedicated API endpoint, to ensure that stale keys cannot be used.
  • Implement an audit procedure to regularly review account status changes and automatically disable or delete API keys that are owned by inactive, suspended, or deleted accounts, and monitor API access logs for unauthorized usage.

Generated by OpenCVE AI on August 12, 2026 at 00:01 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 07 Aug 2026 10:30:00 +0000

Type Values Removed Values Added
First Time appeared Apache
Apache answer
Vendors & Products Apache
Apache answer

Wed, 05 Aug 2026 15:30:00 +0000

Type Values Removed Values Added
Description Insufficient Session Expiration vulnerability in Apache Answer. This issue affects Apache Answer: through 2.0.1. Administrative API keys remained usable after the owning administrator was demoted or the account was marked inactive, suspended, or deleted, allowing continued access until the keys were explicitly removed. Users are recommended to upgrade to version 2.0.2, which fixes the issue.
Title Apache Answer: Residual Administrative API Key Access After Role or Account Revocation
Weaknesses CWE-613
References

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-08-06T17:47:19.743Z

Reserved: 2026-07-08T08:44:04.104Z

Link: CVE-2026-60053

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Analyzed

Published: 2026-08-05T16:16:58.323

Modified: 2026-08-07T13:08:20.460

Link: CVE-2026-60053

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-12T00:15:12Z

Weaknesses
  • CWE-613

    Insufficient Session Expiration