CVE-2026-53644
Authenticated users can read and reset API key secrets for non-active orders.
Is CVE-2026-53644 being exploited?
Not confirmed. CVE-2026-53644 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.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-53644?
CVE-2026-53644 is rated High with a CVSS score of 8.6. 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-53644?
Yes. A fix has been recorded for CVE-2026-53644. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53644 affect?
CVE-2026-53644 affects FOSSBilling 0.5.3–0.7.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53644?
Upgrade to 0.8.0+; or remove Serviceapikey module; or block endpoints with a WAF.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated API users can read and reset service API keys for non-active orders, risking key leakage and account compromise.
Immediate action required
- affected>= 0.5.3 and < 0.8.0
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.