Quick answers
- Is CVE-2026-79613 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-79613 being exploited in the wild.
- How severe is CVE-2026-79613?
- Informational severity, published 19 October 2026.
- Which products and versions are affected?
- Apache Answer through 2.0.2.
- Is there a fix for CVE-2026-79613?
- Yes: fixed in 2.0.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-79613 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-79613?
- Check whether you run Apache Answer 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
- Fixed in: 2.0.3
Technical details
The vulnerability allows unauthenticated attackers to access comments associated with non-public content through the public user profile interface. The issue affects Apache Answer versions through 2.0.2, where insufficient access controls permit viewing restricted content metadata via profile enumeration.
Affected products
- Apache Answer through 2.0.2
Timeline
- 2026-10-19: advisory