CVE-2026-45336
Hard-coded Flask secret_key allows forging admin session cookies, bypassing authentication.
Is CVE-2026-45336 being exploited?
Not confirmed. CVE-2026-45336 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.62% probability of exploitation in the next 30 days.
How severe is CVE-2026-45336?
CVE-2026-45336 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-45336?
Yes. A fix has been recorded for CVE-2026-45336. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-45336 affect?
CVE-2026-45336 affects HireFlow <= 1.2, app.py hard-coded Flask secret_key. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-45336?
Upgrade to HireFlow 1.3, rotate secret_key and invalidate all sessions.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can forge session cookies using the known secret_key to gain admin privileges, access/modify candidate data and schedules.
Immediate action required
- affected< 1.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.