Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain valid global API key
-
ExploitQuery MCP answer-retrieval tool
-
ExecutionRequest answers for hidden/deleted/pending questions
-
ImpactReceive non-public content
Vulnerability Assessment
| Exploitation Conditions | Exploitation requires (1) an Apache Answer deployment at version 2.0.2 or earlier with the MCP (Model Context Protocol) answer-retrieval tool exposed/enabled, and (2) the attacker to hold a valid global API key for that instance. The authorization defect is in the MCP tool's failure to honor per-question visibility (hidden, deleted, pending-review) states. Limiting factors: this is NOT unauthenticated - a legitimate global API key is a prerequisite, so the realistic threat is a key holder (insider, integration, or leaked key) rather than an anonymous remote attacker; instances that do not use the MCP integration are not exposed. Impact is limited to disclosure of answer content for non-public questions; no modification or denial of service is implied by the description. |
| Impact | This is a moderate-severity information-disclosure issue (Missing Authorization, CWE-862 class) that realistically sits below true patch-now priority. No CVSS vector, EPSS score, KEV listing, or POC was provided in the input, so there is no signal of active or imminent exploitation - exploitation status is therefore 'no public exploit identified at time of analysis.' The real-world risk is constrained by two facts drawn from the description: exploitation is not anonymous (it requires possession of a 'global API key'), and the impact is bounded to reading answer content tied to hidden, deleted, or pending-review questions - there is no indication of write, integrity, or availability impact. One signal to flag explicitly: NO CVSS vector was supplied by NVD or the vendor, so attack vector, complexity, and privilege level are INFERRED from the description text, not confirmed - authentication requirements should be verified against the Apache advisory. The 'global API key' prerequisite strongly suggests a privileged/trusted-integration credential, which both lowers mass-exploitation likelihood and means the most plausible abuse is by an insider or a leaked/over-shared key rather than internet-wide scanning. Net: a legitimate confidentiality bug worth patching in affected deployments, but not an emergency absent any exploitation evidence. |
| Exploit ScenarioDerived | An actor holding a valid global API key for an Apache Answer instance (<=2.0.2) that exposes the MCP answer-retrieval tool queries the tool for answers belonging to questions that are hidden, deleted, or still in pending review. Because the tool fails to enforce per-question visibility authorization, it returns content the key holder should not be able to see, disclosing non-public Q&A material. No public 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
Improper authorization in Apache Answer 2.0.2 and earlier allows holders of a valid global API key to retrieve answer content tied to questions that are hidden, deleted, or still pending review. The defect is in the MCP (Model Context Protocol) answer-retrieval tool, which returns content without honoring the per-question visibility state, so an authenticated key holder - an insider, a third-party integration, or anyone using a leaked key - can read material the Q&A platform intended to withhold. It is not reachable by anonymous remote attackers, impact is limited to information disclosure with no modification or denial of service, and no public exploit identified at time of analysis; CISA KEV does not list this issue.
RemediationAI
Upgrade Apache Answer to version 2.0.3, which the vendor states fixes the authorization check in the MCP answer-retrieval tool; this is the only complete remediation because the defect is in server-side access control that cannot be corrected by configuration on 2.0.2 or earlier. If upgrading cannot be done immediately, the most effective compensating control is to disable or unexpose the MCP integration on the affected instance - that removes the vulnerable retrieval path entirely, at the cost of losing MCP-driven answer retrieval for any connected agents or tooling until the upgrade is applied. As a secondary measure, inventory and rotate global API keys, revoke keys held by integrations that no longer need MCP access, and avoid issuing global-scope keys to callers that only require per-user or limited scopes; rotating keys will break existing integrations until they are reconfigured with the new credential. Operators should also confirm that hidden, deleted, and pending-review content on 2.0.2-or-earlier instances has not been harvested through the MCP endpoint, since disclosure leaves no trace in question visibility state. Vendor and advisory references: https://answer.apache.org, https://seclists.org/oss-sec/2026/q4/202, and https://www.cve.org/CVERecord?id=CVE-2026-71563.
Affected ProductsAI
Apache Answer, all releases through 2.0.2, is affected; the issue was reported to the Apache security process and is fixed in 2.0.3. The relevant exposure surface is the MCP answer-retrieval tool bundled with those releases, so only Apache Answer instances that have the MCP integration exposed or enabled at 2.0.2 or earlier carry the risk. No CPE identifiers were included in the supplied intelligence, and no third-party products are named as affected. The Apache project page at https://answer.apache.org serves as the vendor reference alongside the oss-security advisory thread at https://seclists.org/oss-sec/2026/q4/202 and the CVE record at https://www.cve.org/CVERecord?id=CVE-2026-71563.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is a Missing Authorization defect in the CWE-862 class: the Model Context Protocol (MCP) answer-retrieval tool exposed by Apache Answer fails to enforce the same per-question visibility rules that the normal web UI and REST endpoints apply. Questions in Apache Answer carry states such as public, hidden, deleted, and pending review; the MCP retrieval path apparently resolves and returns answer bodies keyed by question identifier without first checking whether the calling principal is entitled to view the parent question's content. Authentication is handled by a global API key rather than per-user session or per-object ownership checks, which means the key's scope - not the individual question's access control list - is the only gate, and a global key effectively bypasses question-level restrictions it was never meant to grant. The assessed vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N reflects network reachability but a low-privilege, credentialed prerequisite, with the exploit chain technically simple once a key is held. No CPE strings or CWE identifier were supplied in the source data, but the affected distribution is Apache Answer through version 2.0.2, and the vulnerability is confined to deployments that expose the MCP integration - instances without MCP enabled have no reachable code path for the flaw.
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
Remote API access over network (AV:N/AC:L) but requires a valid global API key (PR:L, possibly PR:H if admin-only); impact is limited confidentiality disclosure only (C:L, I:N, A:N).
Description PRE-NVD
Executive ViewAI
Organizations running Apache Answer 2.0.2 or earlier may be leaking Q&A content that was deliberately hidden, deleted, or still awaiting review, because the platform's MCP answer-retrieval tool does not enforce per-question visibility rules. The exposure is limited to information disclosure and requires a valid global API key, meaning the risk sits with internal staff, third-party integrations, and any leaked or over-shared credential rather than with anonymous outsiders. With no vendor patch currently available, leadership attention should focus on API key hygiene, monitoring, and tracking Apache's advisory for a fixed release.
No vendor-released patch identified at time of analysis. Interim mitigations: rotate and revoke global API keys, shorten key lifetimes and scope keys per integration, disable or network-restrict the MCP answer-retrieval tool, monitor and alert on key-based retrieval of hidden, deleted, or pending-review content, and restrict access to the Apache Answer environment to trusted networks.
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.
CVE.org
GitHub PoC
Exploit-DB