Vulnerability in github.com/apache/incubator-answer (CVE-2026-25699)
Summary
Vulnerability in github.com/apache/incubator-answer (CVE-2026-25699). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.7.2-0.20260206073245-92994b49976b or later.
Original description
The description as published by the source.
Exposure of Private Personal Information to an Unauthorized Actor vulnerability in Apache Answer.
This issue affects Apache Answer: through 2.0.0.
Timeline-related APIs lacked proper authorization checks, allowing regular authenticated users to access deleted, private, or unapproved content and its revision history.
Users are recommended to upgrade to version 2.0.1, which fixes the issue.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-25699 has been found in github.com/apache/incubator-answer.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade github.com/apache/incubator-answer to 1.7.2-0.20260206073245-92994b49976b or later.
If unsure, ask your IT team or search "github.com/apache/incubator-answer CVE-2026-25699" on the vendor's site.
CVE-2026-25699 (github.com/apache/incubator-answer) — CWE-359 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.7.2-0.20260206073245-92994b49976b — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-359) exists in github.com/apache/incubator-answer.
Check the vendor advisory for the affected versions of github.com/apache/incubator-answer.
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.
Update to 1.7.2-0.20260206073245-92994b49976b.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/apache/incubator-answer' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/apache/incubator-answer' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/apache/incubator-answerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/apache/incubator-answer to 1.7.2-0.20260206073245-92994b49976bステージング環境で 1.7.2-0.20260206073245-92994b49976b に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web lists.apache.org
- web openwall.com
- web github.com
- web github.com