Is CVE-2026-25699 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-25699 being exploited in the wild.

How severe is CVE-2026-25699?

Medium severity, with a CVSS score of 6.1, published 9 June 2026.

Which products and versions are affected?

Apache Software Foundation Answer through 2.0.0; github.com/apache/answer (Go) SEMVER:introduced=0,fixed=1.7.2-0.20260206073245-92994b49976b; github.com/apache/incubator-answer (Go) < 1.7.2-0.20260206073245-92994b49976b, SEMVER:introduced=0,fixed=1.7.2-0.20260206073245-92994b49976b.

Is there a fix for CVE-2026-25699?

Yes. github.com/apache/answer (Go): upgrade to 1.7.2-0.20260206073245-92994b49976b or later; github.com/apache/incubator-answer (Go): upgrade to 1.7.2-0.20260206073245-92994b49976b or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-25699 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-25699?

Check whether you run Apache Software Foundation Answer, github.com/apache/answer (Go) or github.com/apache/incubator-answer (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-25699: Apache Answer information disclosure in timeline APIs

Q: Is there a fix for CVE-2026-25699?

Yes. github.com/apache/answer (Go): upgrade to 1.7.2-0.20260206073245-92994b49976b or later; github.com/apache/incubator-answer (Go): upgrade to 1.7.2-0.20260206073245-92994b49976b or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-25699 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-25699?

Check whether you run Apache Software Foundation Answer, github.com/apache/answer (Go) or github.com/apache/incubator-answer (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-25699 · Severity: medium · CVSS 6.1 · Published 2026-06-09

Apache Answer is an open-source Q&A platform used by organizations to build knowledge-sharing communities. A security flaw in the platform's timeline features allowed standard users to bypass security restrictions and view private, deleted, or unapproved content. This could lead to the exposure of sensitive personal information or internal discussions that were intended to be hidden or removed.

Technologies: Apache Software Foundation Answer, github.com/apache/answer (Go), github.com/apache/incubator-answer (Go). Vendors: Apache Software Foundation, Go.

Quick answers

Is CVE-2026-25699 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-25699 being exploited in the wild.
How severe is CVE-2026-25699?: Medium severity, with a CVSS score of 6.1, published 9 June 2026.
Which products and versions are affected?: Apache Software Foundation Answer through 2.0.0; github.com/apache/answer (Go) SEMVER:introduced=0,fixed=1.7.2-0.20260206073245-92994b49976b; github.com/apache/incubator-answer (Go) < 1.7.2-0.20260206073245-92994b49976b, SEMVER:introduced=0,fixed=1.7.2-0.20260206073245-92994b49976b.
Is there a fix for CVE-2026-25699?: Yes. github.com/apache/answer (Go): upgrade to 1.7.2-0.20260206073245-92994b49976b or later; github.com/apache/incubator-answer (Go): upgrade to 1.7.2-0.20260206073245-92994b49976b or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-25699 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-25699?: Check whether you run Apache Software Foundation Answer, github.com/apache/answer (Go) or github.com/apache/incubator-answer (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/apache/answer (Go): upgrade to 1.7.2-0.20260206073245-92994b49976b or later
```
go get github.com/apache/answer@v1.7.2-0.20260206073245-92994b49976b
```
github.com/apache/incubator-answer (Go): upgrade to 1.7.2-0.20260206073245-92994b49976b or later
```
go get github.com/apache/incubator-answer@v1.7.2-0.20260206073245-92994b49976b
```

Technical details

An authorization bypass vulnerability exists in Apache Answer versions through 2.0.0 within the timeline-related APIs. The root cause is a lack of proper authorization checks in the ActivityController, specifically within the GetObjectTimeline and GetObjectTimelineDetail functions. An authenticated attacker can exploit this by sending crafted requests to these APIs to access deleted, private, or unapproved content and its revision history. The vulnerability is addressed in version 2.0.1 by implementing mandatory visibility checks and verifying administrative/moderator privileges via middleware before returning timeline objects.

Affected products

Apache Answer through 2.0.0

Identifiers

CVE-2026-25699
GHSA-w754-5646-xq9j
GO-2026-6148

Timeline

2026-06-09: disclosed
2026-06-09: advisory
2026-02-06: patched: Fix committed to repository

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.