Skip to content

AAK-MCP-APACHEANSWER-CVE-2026-71563-001: Apache Answer image 2.0.0 to 2.0.2: the MCP answer tool returns answers to hidden, deleted and pending questions

Severity
MEDIUM
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/container_image_pins.py
Auto-fixable
No.
SARIF name
ApacheAnswerMcpNonPublicAnswerRead

What it detects

Apache Answer, a self-hosted Q&A platform, serves MCP tools over SSE from 2.0.0, behind an API key and a site switch that a fresh install turns on. Its answer tool lists the answers to whatever question id it is given and checks only each answer's own status, not whether the question is public, so whoever holds a global API key reads answers to hidden, deleted and pending-review questions (CVE-2026-71563, CWE-862). Checked in the source: internal/controller/mcp_controller.go is absent at 1.7.1 and arrives in 2.0.0-RC1, and MCPAnswersHandler reads the same way through 2.0.2. 2.0.3 (63a67542, "fix: constrain MCP content access") returns nothing unless the question is shown and available or closed, and puts the same check on the question-detail and comment tools. MEDIUM follows the ASF's own rating, moderate; neither NVD nor the CVE record gives a CVSS score.

How to fix

Upgrade the apache/answer image to 2.0.3 or later and pin the tag. Until then, turn MCP off in the admin settings, or give a global API key only to someone who may read hidden, deleted and pending-review content.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-APACHEANSWER-CVE-2026-71563-001

Limitations

Reads apache/answer tags from 2.0.0 below 2.0.3 in compose files, Kubernetes manifests, Helm values, Dockerfiles and MCP configs. A release candidate reads as its release, so 2.0.3-RC1, built from the 2.0.3 commit, is not reported. latest was a 2.0.3 build on 2026-10-19, fixed, and the compose file and Helm chart in Answer's repository use it, so an untagged or latest reference is not reported. It reads the version, not whether MCP is switched on or an API key exists. An install from the release binaries or the Go module is not read, nor is the docker.io/apache/answer spelling, and an MCP client config names the endpoint by URL, which states no version.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-APACHEANSWER-CVE-2026-71563-001.md: the page then shows that text, with the registry reference appended under it.