GHSA-4w4v-prg2-9h29
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify non-public question ID
-
ExploitRequest invited-user list endpoint
-
ImpactDisclose invited user identities
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the target Apache Answer instance (version through 2.0.2) contains non-public questions that have an associated invited-user list, and that the attacker can reach and invoke the invited-user lookup functionality for such a question - likely needing a valid or guessable question identifier. The advisory states an unauthenticated or unauthorized user can succeed, implying no special configuration is needed beyond the default presence of the invite feature; however, this is not confirmed by a CVSS vector. Limiting factors: impact is confined to disclosure of the invited-user list for private questions (no modification or service impact), the instance must actually use private questions with invites, and the attacker must know or enumerate the relevant question. Upgrading to 2.0.3 removes the condition entirely. |
| Impact | This is a genuinely low-priority issue, consistent with the vendor's 'low' severity rating. The vulnerability is an information-disclosure flaw (missing authorization check) that exposes the invited-user list of a non-public question in Apache Answer - a limited confidentiality leak with no integrity or availability impact. No CVSS vector, EPSS score, KEV listing, SSVC decision, or POC was provided in the input, so several key prioritization signals are missing and cannot be cross-referenced. Status: no public exploit identified at time of analysis, and there is no evidence of active exploitation. The description claims an 'unauthenticated or unauthorized user' can trigger it, which would normally map to a network, no-privilege vector; however, because no CVSS vector was supplied, authentication requirements are not independently confirmed from the available data and rest solely on the advisory prose. Net assessment: a real but low-impact authorization bug worth patching during normal maintenance cycles, not an emergency - the exposed data (who was invited to a private question) is sensitive in a narrow sense but not high-value, and the affected product has a modest deployment footprint. |
| Exploit ScenarioDerived | An attacker who is not authorized to view a private (non-public) question on an Apache Answer instance queries the invited-user lookup functionality for that question and receives back the list of invited users, revealing identities/relationships that should have been hidden. Because the advisory states an unauthenticated or unauthorized user can do this, the request likely requires only knowledge or enumeration of a target question identifier. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
Missing visibility authorization checks in Apache Answer through 2.0.2 let remote, unauthenticated attackers retrieve the invited-user list attached to non-public questions that they should not be able to see. The flaw is limited to information disclosure - an attacker who can reach the invite-lookup functionality and reference a private question identifier can enumerate the users invited to that question, but cannot modify content or disrupt the service. The vendor rates this low severity, our independent assessment concurs (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), no public exploit code has been identified at time of analysis, there is no indication of confirmed active exploitation, and no EPSS score was supplied; upgrading to Apache Answer 2.0.3 resolves the issue.
RemediationAI
Upgrade to Apache Answer 2.0.3, the vendor-released fix for this issue (announced at https://seclists.org/oss-sec/2026/q4/201 and referenced from https://answer.apache.org and the CVE record https://www.cve.org/CVERecord?id=CVE-2026-68482); this is the only complete remediation and carries no functional trade-off beyond the normal version upgrade. If the upgrade cannot be scheduled immediately, the exposure is narrow enough that targeted compensating controls are viable: place the question invite-lookup endpoint behind an authentication requirement at the reverse proxy or API gateway so anonymous callers cannot invoke it at all (trade-off: legitimate public-facing invite flows that rely on anonymous access would break, and the endpoint path must be confirmed against your deployment), or restrict network access to the Answer instance to trusted IP ranges while unpatched (trade-off: reduces the platform's intended public reach, so it is usually impractical for a community forum). Because impact is limited to disclosure of invited-user lists for private questions, a lower-cost interim measure is to audit and remove invite lists from non-public questions or convert sensitive private questions out of the invite model until patched, accepting that private collaboration via invites is degraded. Monitor instance logs for unexpected calls to invite-related API routes referencing question identifiers the caller does not own. Do not rely on the low CVSS score as a reason to skip the patch indefinitely - the missing authorization check is trivially reachable by unauthenticated callers - but do treat it as a low-urgency item relative to higher-impact work.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in 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 for teams, and the vulnerable logic lives in its question "invite user" functionality. Answer supports questions with differing visibility (public versus non-public/private), and private questions may carry an invite list naming the users who are permitted to see them. The invite-lookup code path returns that list without first re-checking whether the requester is authorized to view the underlying question, a classic missing-authorization / broken object-level authorization condition (in CWE terms, the missing-authorization family rather than an injection or memory-safety bug). Because the authorization decision depends on the question's visibility and the caller's identity rather than on any cryptographic or parser weakness, the exposure is confined to metadata: the names of users associated with a private question. It does not, per the advisory and the assessed vector (C:L, I:N, A:N, S:U), grant write access, session compromise, or denial of service. Exploitation requires the target instance to actually use private questions with invite lists and the attacker to reach the lookup endpoint and supply or guess a valid question identifier; instances that never use private-question invites are unaffected in practice. No CPE entries or CWE identifier were supplied in the source data, so the affected product-family identification rests on the vendor's own advisory naming Apache Answer through 2.0.2.
Know when the next one hits your stack
- 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
Web-reachable (AV:N), no privileges per advisory's unauthenticated/unauthorized claim (PR:N), no interaction (UI:N); only a limited user list is leaked, so C:L and I/A:N.
Estimated by vuln.today — no official severity rating has been published for this CVE yet.
Description PRE-NVD
Threat Intelligence Overview
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.
What every action level means
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-104157
CVE.org
EPSS
Exploit-DB