CVE-2026-53431
Expired JWT replay lets attacker authenticate as an OAuth client.
Is CVE-2026-53431 being exploited?
Not confirmed. CVE-2026-53431 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.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-53431?
CVE-2026-53431 is rated Critical with a CVSS score of 9.1. 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-53431?
Yes. A fix has been recorded for CVE-2026-53431. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53431 affect?
CVE-2026-53431 affects malach-it Boruta >=2.3.0 and <2.3.7. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53431?
Upgrade Boruta to >=2.3.7; rotate client keys/secrets and audit for leaked assertions.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Replay of expired JWT client assertions allows attackers to obtain access tokens as the client, enabling unauthorized access and privilege abuse.
Immediate action required
- affected>= 2.3.0 and < 2.3.7
- affected>= 5bfbe1c5443bffe71cf1bf954bbdff61327d9a83 and < *
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.