GHSA-8gxm-7cvr-5vpw
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAccess public user profile
-
ExploitEnumerate profile comment activity
-
ExecutionRead comments on non-public content
-
ImpactHarvest restricted information
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V14 - Data Protection Sensitive data in outbound message
|
| Exploitation Conditions | Exploitation requires a deployed Apache Answer instance (version 2.0.2 or earlier) where non-public content exists and users with activity on that content have publicly accessible profiles; the disclosure occurs via those public user profiles. No authentication is required, limiting prerequisites to network reachability of the Answer web interface. Realistic exposure is constrained to instances that actually host non-public/restricted content - a purely public Q&A deployment has little to leak. Impact is limited to disclosure of comments associated with that non-public content, not the content bodies themselves, credentials, or any write/modify capability. |
| Impact | This is a moderate-severity information disclosure flaw in Apache Answer (through 2.0.2) that is a genuine but bounded access-control issue rather than a top-priority emergency. No CVSS vector, EPSS score, KEV listing, or SSVC decision data was provided in the input, so quantitative exploitation-probability and automatability signals are entirely absent and cannot be compared. Based on the description alone, exploitation is unauthenticated and appears to require only normal access to public user profiles, which makes the technical barrier low; however, the impact is narrow - exposure of comments tied to non-public content, not full content, credentials, or write access. There is no public exploit identified at time of analysis and no evidence of active exploitation, so this reads as a real priority for operators of self-hosted Answer instances with private/non-public spaces, but not a widespread mass-exploitation threat. The headline 'moderate' rating is consistent with low confidentiality-only impact; defenders should patch to 2.0.3 on normal maintenance cadence rather than as an out-of-band emergency unless they host sensitive non-public communities. |
| Exploit ScenarioDerived | An unauthenticated attacker browses a public user profile on a self-hosted Apache Answer instance and, through the profile's exposed activity, retrieves comments that were associated with non-public (restricted or private) content they should not be able to read. Because no authentication is required, the attacker needs only network access to the Answer web application. No public proof-of-concept exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
Unauthenticated information disclosure in Apache Answer through 2.0.2 allows remote attackers to read comments tied to non-public (restricted) content by browsing public user profiles, which are rendered without re-checking the visibility of the parent content. The issue is network-reachable, requires no authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), and is bounded to comment disclosure - no content bodies, credentials, or write capability are exposed, and instances hosting only public Q&A material have little to leak. No public exploit code has been identified at time of analysis and there is no indication of active exploitation; users should upgrade to version 2.0.3, which fixes the issue.
RemediationAI
Upgrade to Apache Answer 2.0.3, the vendor-released version that fixes this issue, and verify the running build after deployment; consult the upstream advisory at https://seclists.org/oss-sec/2026/q4/204 and the project site at https://answer.apache.org for the release notes and download artifacts. Until the upgrade can be staged, an effective compensating control is to make user profiles non-public or restrict profile visibility to authenticated users, which removes the disclosure path entirely at the cost of losing profile-based reputation and community browsing features; alternatively, remove or tighten visibility of non-public content that has comments, or place the instance behind an authenticated reverse proxy so anonymous browsing of the profile endpoints is blocked - both reduce the exposure but trade away public/SEO access to the site. Because the flaw is read-only and requires no credentials, no log-correlation or credential-rotation response is needed, but administrators should review comments on restricted content for anything sensitive that may already have been exposed. If the platform cannot be patched or reconfigured in the near term, limiting network reachability of the Answer web interface to trusted networks is a last-resort mitigation with significant usability impact.
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 that structures users, questions, answers, comments, and tags into a searchable knowledge base, with user profiles that aggregate a member's activity. The flaw is a broken access-control issue in the profile aggregation path: when a public profile lists a user's comments, the application returns comments attached to content that is not publicly visible, instead of filtering those entries against the visibility state of the parent question or answer. This falls into the improper access control / authorization-bypass weakness class (CWE-284/CWE-639 family), where an object's access decision is not enforced at every retrieval path - here the profile view is a secondary path that bypasses the restriction enforced on the primary content view. Because the vulnerable endpoint is a profile page served by the web front end, exploitation requires only network reachability of the Answer instance and the existence of at least one user with comments on non-public content; the CVSS vector's PR:N/UI:N confirms no authentication or interaction prerequisite.
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
Unauthenticated network access via public profiles (AV:N/AC:L/PR:N/UI:N) yields only partial confidentiality disclosure of comments (C:L), with no integrity or availability impact.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-104160
CVE.org
EPSS
Exploit-DB