Live › vulnerability › CVE-2026-67249
Go to dashboardApache Answer does not check the purpose of an email verification code, so a code issued for one workflow can be accepted by another sensitive workflow. An attacker who obtains a valid code for one email-based action could use it to complete a different sensitive action.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running Apache Answer through version that use email verification codes for account actions. Sources do not say which workflows are sensitive or how common the affected setup is, so exposure beyond the version check is unknown.
2.0.2No product ranges from the sources yet.
2.0.2 or earlier.2.0.3 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A vulnerability in Apache Answer.
This issue affects Apache Answer: through 2.0.2.
A verification code issued for one email-based workflow could be accepted by another sensitive workflow because the code purpose was not properly enforced.
Users are recommended to upgrade to version 2.0.3, which fixes the issue.
This page as .md · .json · in your agent: get_signal("CVE-2026-67249")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.