Skip to main content

Apache Answer CVE-2026-25700

| EUVDEUVD-2026-36059 HIGH
Improper Restriction of Security Token Assignment (CWE-1259)
2026-06-10 apache GHSA-4gw2-vg4x-7p29
7.2
CVSS 3.1 · Vendor: apache
View

Attack ChainAIDerived

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

  1. Access
    Obtain admin token while account active
  2. Delivery
    Account suspended or deleted by operator
  3. Exploit
    Continue calling admin API with retained token
  4. Execution
    Server skips account-state revocation check
  5. Persist
    Modify configuration or exfiltrate data
  6. Impact
    Maintain access until token TTL expires

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Hardware security identifier management
Exploitation Conditions

Exploitation requires the attacker to possess a previously issued administrative token from Apache Answer 2.0.0 or earlier, obtained while the associated account was in good standing (CVSS PR:H). The vulnerable behavior is triggered specifically when an administrator account undergoes a state change - suspension, deletion, or deactivation - and the operator expects that change to terminate access; the issue does not arise against accounts that simply log out or whose tokens expire normally. Exploitation is bounded by the original token's natural expiration time (set by the deployment's token TTL configuration) and is limited to administrative API surface, not arbitrary user accounts.

Impact

Signals are mixed and skew lower than the 7.2 CVSS suggests for most defenders. CVSS lists AV:N/AC:L/PR:H/UI:N with C:H/I:H/A:H, but PR:H means the attacker must already have administrator credentials and a valid token - meaning this is fundamentally a post-compromise persistence/insider-threat issue, not a remote takeover. SSVC reinforces this: Exploitation=none, Automatable=no, Technical Impact=total - high impact if abused but no automation potential and no observed exploitation. No CISA KEV listing and no public PoC is referenced. The realistic risk is highest in environments that rotate admin staff and rely on account suspension as a primary off-boarding control without forcing token revocation; for those operators, this is a genuine concern despite the modest exploitation signals.

Exploit ScenarioDerived

An organization off-boards a compromised or departing administrator by suspending their Apache Answer account, assuming this revokes access. The former admin (or anyone who captured their token) continues calling administrative endpoints - modifying site configuration, deleting content, or exfiltrating user data - using the still-valid bearer token until it expires naturally. No public PoC is referenced in the advisory.

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

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

Alert me

AnalysisAIv1 – Jun 10, 2026

Privilege persistence in Apache Answer through version 2.0.0 allows suspended, deleted, or deactivated administrator accounts to retain access to administrative APIs because previously issued tokens are not invalidated upon account state change. The flaw requires high-privilege access to obtain a token initially and carries a CVSS 7.2 with full confidentiality, integrity, and availability impact; no public exploit identified at time of analysis and SSVC marks exploitation as none.

RemediationAI

Vendor-released patch: upgrade to Apache Answer 2.0.1, which the advisory at https://lists.apache.org/thread/ftw52mlxknjm29vo1mnqovj53z2kh96y identifies as the fixed release. Until the upgrade is applied, operators off-boarding an administrator should not rely solely on account suspension or deletion; rotate the underlying token/session secret (forcing all admin tokens to invalidate), shorten administrative token lifetimes in configuration so the exposure window after suspension is minutes rather than days, and audit admin API access logs for activity by removed accounts. The trade-off of forced rotation is that all current admin sessions must re-authenticate, and shorter token lifetimes increase login friction for legitimate admins.

Affected VersionsENISA

Apache Answer 0 ≤2.0.0

Affected Packages

go github.com/apache/answer fix: 2.0.1
go github.com/apache/incubator-answer fix: 2.0.1
euvd apache_answer no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 3 packages in go, euvd

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

Technical ContextAI · show details

Apache Answer is an open-source Q&A community platform maintained by the Apache Software Foundation, used to build knowledge-sharing sites. The root cause maps to CWE-1259 (Improper Restriction of Security Token Assignment), meaning the application's session/token lifecycle logic does not tie token validity to the underlying account state. When an admin is suspended, deleted, or deactivated, the server-side authorization checks continue to honor the existing bearer/session token until its natural expiration, rather than performing a revocation or state lookup on each privileged API call. CPE data confirms the affected component is cpe:2.3:a:apache_software_foundation:apache_answer.

Know when Apache Answer 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.2 HIGH
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
SUSE HIGH

Primary rating from Vendor (apache).

CVSS VectorVendor: apache

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

Lifecycle Timeline

3
CVSS changed
Jun 10, 2026 - 17:22 NVD
7.2 (HIGH)
CVE Published
Jun 10, 2026 - 14:57 nvd
UNKNOWN (no severity yet)
CVE Published
Jun 10, 2026 - 14:57 nvd
HIGH 7.2

DescriptionCVE.org

Improper Restriction of Security Token Assignment vulnerability in Apache Answer.

This issue affects Apache Answer: through 2.0.0.

Previously issued administrative tokens were not invalidated after an administrator account was suspended, deleted, or deactivated, allowing continued access to administrative APIs until the token expired. Users are recommended to upgrade to version 2.0.1, which fixes the issue.

Executive ViewAI

Why It Matters

Apache Answer deployments running version 2.0.0 or earlier contain a privilege persistence flaw allowing deactivated, suspended, or deleted administrator accounts to maintain full administrative access through previously-issued session tokens. This prevents effective account revocation for departed employees or compromised admins, creating a residual unauthorized access risk to sensitive systems and data. Organizations using Answer for internal information management must implement interim controls immediately, as no vendor patch is currently available.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Implement continuous monitoring and alerting for administrative API access patterns, with immediate escalation for activity from deactivated accounts; (2) Deploy forced re-authentication requirement for all administrators immediately after any account suspension, deletion, or deactivation; (3) Maintain detailed audit logs of all API activity with administrative access as focus area; (4) Restrict administrative API access to segmented networks with restricted source IP ranges; (5) Prioritize account suspension over deletion to maintain revocation audit trail while compensating controls are in effect.

Threat Intelligence Overview

EPSS Score
0.0%
Top 89% exploitable
Threat Intel
1
1 sources
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA Vendor VulDB

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.0%
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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
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.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Server 16.1 Affected
SUSE Linux Enterprise Server for SAP applications 16.1 Affected

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