CVE-2026-46657

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Bludit is a content management system. Versions prior to 3.22.0 have a vulnerability in the user management logic that allows deactivated accounts to maintain access via persistent authentication tokens. When an administrator disables a user account, the application fails to invalidate or clear the associated tokenAuth and tokenRemember fields in the JSON database. Consequently, any user with a pre-existing "Remember Me" cookie can bypass the account disablement and maintain a valid authenticated state. Version 3.22.0 patches the issue.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
18.8%
KEV
Not listed

Published

June 8, 2026

Last Modified

June 9, 2026

Advisory Details (2)

Auto-updated Jun 11, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_release.
github Patch Available🟡 PoC Available

Persistent Authentication Tokens not Revoked upon Account Disablement · Advisory · bludit/bludit · GitHub

https://github.com/bludit/bludit/security/advisories/GHSA-ggqg-xvx6-hgwh
github_release Patch Available

Bludit v3.22.0

Patch available: bludit/bludit 3.22.0

https://github.com/bludit/bludit/releases/tag/3.22.0

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 80× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 10:41 UTCEG score recompute
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-10 21:31 UTCEG score recompute
  4. 2026-07-09 19:10 UTCEPSS rescore
  5. 2026-07-09 05:46 UTCEG score recompute
  6. 2026-07-08 16:39 UTCEG score recompute
  7. 2026-07-08 15:16 UTCEPSS rescore
  8. 2026-07-08 03:32 UTCEG score recompute
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-05 17:40 UTCEG score recompute
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-04 15:06 UTCEG score recompute
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-03 16:20 UTCEG score recompute
  17. 2026-07-02 22:22 UTCEG score recompute
  18. 2026-07-02 09:13 UTCEG score recompute
  19. 2026-07-01 20:03 UTCEG score recompute
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-07-01 06:57 UTCEG score recompute
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 16:31 UTCEG score recompute
  24. 2026-06-29 21:21 UTCEG score recompute
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 66 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-29 08:14 UTCEG score recompute
  3. 2026-06-28 17:24 UTCEG score recompute
  4. 2026-06-28 14:07 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-28 04:17 UTCEG score recompute
  8. 2026-06-27 15:11 UTCEG score recompute
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-27 02:03 UTCEG score recompute
  11. 2026-06-26 12:49 UTCEG score recompute
  12. 2026-06-25 23:38 UTCEG score recompute
  13. 2026-06-25 13:49 UTCEPSS rescore
  14. 2026-06-25 10:31 UTCEG score recompute
  15. 2026-06-24 21:23 UTCEG score recompute
  16. 2026-06-24 14:05 UTCEPSS rescore
  17. 2026-06-24 08:17 UTCEG score recompute
  18. 2026-06-23 21:33 UTCEPSS rescore
  19. 2026-06-23 21:33 UTCEPSS rescore
  20. 2026-06-23 16:09 UTCEG score recompute
  21. 2026-06-22 22:47 UTCEG score recompute
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-22 05:51 UTCEG score recompute
  25. 2026-06-21 14:56 UTCEPSS rescore
  26. 2026-06-21 14:56 UTCEPSS rescore
  27. 2026-06-21 11:03 UTCEG score recompute
  28. 2026-06-21 01:59 UTCEPSS rescore
  29. 2026-06-21 01:59 UTCEPSS rescore
  30. 2026-06-20 21:54 UTCEG score recompute
  31. 2026-06-20 08:04 UTCEG score recompute
  32. 2026-06-19 19:26 UTCEPSS rescore
  33. 2026-06-19 19:26 UTCEPSS rescore
  34. 2026-06-19 14:46 UTCEG score recompute
  35. 2026-06-19 01:37 UTCEG score recompute
  36. 2026-06-18 17:52 UTCEPSS rescore
  37. 2026-06-18 17:52 UTCEPSS rescore
  38. 2026-06-18 11:51 UTCEG score recompute
  39. 2026-06-17 22:43 UTCEG score recompute
  40. 2026-06-17 17:53 UTCEPSS rescore
  41. 2026-06-17 09:36 UTCEG score recompute
  42. 2026-06-16 20:30 UTCEG score recompute
  43. 2026-06-16 17:53 UTCEPSS rescore
  44. 2026-06-16 07:22 UTCEG score recompute
  45. 2026-06-15 18:15 UTCEG score recompute
  46. 2026-06-15 17:49 UTCEPSS rescore
  47. 2026-06-15 05:05 UTCEG score recompute
  48. 2026-06-14 15:58 UTCEG score recompute
  49. 2026-06-14 02:51 UTCEG score recompute
  50. 2026-06-13 23:00 UTCEPSS rescore
  51. 2026-06-13 13:44 UTCEG score recompute
  52. 2026-06-13 00:36 UTCEG score recompute
  53. 2026-06-12 23:12 UTCEPSS rescore
  54. 2026-06-12 23:12 UTCEPSS rescore
  55. 2026-06-12 11:29 UTCEG score recompute
  56. 2026-06-11 22:22 UTCEG score recompute
  57. 2026-06-11 14:00 UTCEPSS rescore
  58. 2026-06-11 09:16 UTCEG score recompute
  59. 2026-06-10 22:18 UTCEPSS rescore
  60. 2026-06-10 20:09 UTCEG score recompute
  61. 2026-06-10 13:22 UTCEPSS rescore
  62. 2026-06-10 13:22 UTCEPSS rescore
  63. 2026-06-10 07:03 UTCEG score recompute
  64. 2026-06-09 17:57 UTCEG score recompute
  65. 2026-06-09 04:51 UTCEG score recompute
  66. 2026-06-08 15:43 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-46657?
CVE-2026-46657 is a high vulnerability published on June 8, 2026. Bludit is a content management system. Versions prior to 3.22.0 have a vulnerability in the user management logic that allows deactivated accounts to maintain access via persistent authentication tokens. When an administrator disables a user account, the application fails to invalidate or clear the…
When was CVE-2026-46657 disclosed?
CVE-2026-46657 was first published in the National Vulnerability Database on June 8, 2026, with the most recent update on June 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46657 actively exploited?
CVE-2026-46657 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46657?
CVE-2026-46657 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-46657?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46657, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46657

Explore →

Is Your Infrastructure Affected by CVE-2026-46657?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs