# What is CVE-2026-53646? > CVE-2026-53646 is a security flaw in the software it affects, published on 6 July 2026. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at under 0.1%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.edgeprotect.io/what-is/cve-2026-53646 ## At a glance - **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle. - **Severity:** Not rated (CVSS n/a out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** under 0.1% (latest exploit-likelihood forecast) - **Published:** 6 July 2026 - **Record last updated:** 6 July 2026 - **Affected products:** 0 ## What is CVE-2026-53646? In plain terms Here is what the published record says about this flaw, and what kind of weakness it is. ### The official description FOSSBilling is a free, open-source billing and client management system. In versions 0.5.6 through 0.7.2, when a `ClientPasswordReset` record already exists for a client (from a previous unexpired reset request), subsequent calls to the `reset_password` guest API endpoint reuse the existing token instead of generating a new one. The 15-minute validity window is anchored to the first request's `created_at` timestamp, not the time of the most recent email. An attacker who obtained the original reset link remains able to use it even after the victim requests a new reset, because the original token is never invalidated or rotated. Version 0.8.0 patches the issue. Some workarounds are available. Configure a reverse proxy (e.g., Nginx, Apache, Cloudflare) to apply per-IP rate limiting to the `/client/reset-password` endpoint to minimize the window of opportunity, and/or manually clear expired `client_password_reset` records from the database after a client reports a suspected compromise. ### What kind of flaw is it? - CWE-640: Weak Password Recovery Mechanism for Forgotten Password ## Is CVE-2026-53646 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at under 0.1%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: <0.1%, <0.1%, <0.1%, <0.1%, <0.1%, <0.1%, <0.1%. ### Timeline - 6 July 2026: Published ### How EdgeProtect ranks it Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: key context - Real threat activity around it: key context 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2026-53646? No affected products have been listed for this flaw yet. ## How do I fix CVE-2026-53646? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? EdgeProtect can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the latest update from the vendor. The references list where the vendor has published details. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [github.com](https://github.com/FOSSBilling/FOSSBilling/security/advisories/GHSA-vp66-w6rc-x32p) ## Questions ### What is CVE-2026-53646? CVE-2026-53646 is a security flaw in the software it affects, published on 6 July 2026. Here is what the published record says about this flaw, and what kind of weakness it is. ### How serious is CVE-2026-53646? It has no severity score yet. No sign of exploitation and a low forecast. Patch it in your normal update cycle. ### Is CVE-2026-53646 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at under 0.1%. That can change at any time, which is why we keep watching. ### How do I fix CVE-2026-53646? Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2026-53646 affect you? EdgeProtect keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.edgeprotect.io/register Book a demo: https://www.edgeprotect.io/contact