Quick answers
- Is CVE-2026-67249 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67249 being exploited in the wild.
- How severe is CVE-2026-67249?
- 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-67249?
- Yes: fixed in Apache Answer 2.0.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-67249 attacked?
- It is in a web application.
- Am I affected by CVE-2026-67249?
- 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: Apache Answer 2.0.3
Technical details
The vulnerability stems from insufficient enforcement of the purpose or context of email verification codes in Apache Answer. A verification code generated for one email-based workflow can be reused in another sensitive workflow due to missing validation of the code's intended purpose. This allows context confusion attacks where an attacker intercepts or observes a code from one workflow and applies it to gain unauthorized access to a different workflow.
Affected products
- Apache Answer through 2.0.2
Timeline
- 2026-10-19: disclosed