CVE-2026-58466

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-02. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

AutoBangumi before 3.2.8 contains a hard-coded default credentials vulnerability that allows unauthenticated attackers to authenticate as the administrator by using the publicly known default credentials seeded at startup via add_default_user() in the database user module when the users table is empty. Attackers can submit the default credentials to the authentication login endpoint to gain full control of the application, including RSS feed configuration, downloader configuration, and all authenticated API endpoints.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 2, 2026

Last Modified

July 14, 2026

Advisory Details (4)

Auto-updated Oct 10, 2026
Patch available. Sources: github_release, github_commit.
Web page

AutoBangumi < 3.2.8 - Hard-coded Default Credentials via add_default_user() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/autobangumi-hard-coded-default-credentials-via-add-default-user
GitHub release Patch Available

🌟3.2.8

Patch available: EstrellaXD/Auto_Bangumi 3.2.8

https://github.com/EstrellaXD/Auto_Bangumi/releases/tag/3.2.8
Web page

[Security] Unauthenticated SSRF via /setup/test-downloader · Issue #1041 · EstrellaXD/Auto_Bangumi · GitHub

https://github.com/EstrellaXD/Auto_Bangumi/issues/1041
GitHub commit

commit 487bdfec545e (EstrellaXD/Auto_Bangumi)

Fix landed in EstrellaXD/Auto_Bangumi commit 487bdfec545e — awaiting tagged release

https://github.com/EstrellaXD/Auto_Bangumi/commit/487bdfec545e805ae416e6ddf28651bd274d6a73

Vendor Advisories for CVE-2026-58466(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 455 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 355 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 22:07 UTCEG score recompute
  2. 2026-10-12 22:06 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  4. 2026-10-12 15:53 UTCEG score recompute
  5. 2026-10-12 06:40 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-11 19:36 UTCEG score recompute
  7. 2026-10-11 16:52 UTCEG score recompute
  8. 2026-10-11 14:14 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  18. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  20. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  21. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  22. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  25. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.8% · 54th percentile
Show 75 more
  1. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  2. 2026-09-23 11:09 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-09-23 06:37 UTCEG score recompute
  4. 2026-09-23 06:37 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  6. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  7. 2026-09-18 10:12 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-09-18 06:14 UTCEG score recompute
  9. 2026-09-18 06:14 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  11. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  12. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  13. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  14. 2026-09-14 07:36 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-09-14 03:56 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-09-14 00:15 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-09-13 16:56 UTCEG score recompute
  18. 2026-09-13 16:56 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  20. 2026-09-13 12:45 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-09-13 08:59 UTCEG score recompute
  22. 2026-09-13 08:59 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-09-12 14:15 UTCEG score recompute
  24. 2026-09-12 14:15 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  26. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  27. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  28. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  29. 2026-09-06 14:19 UTCEG score recompute
  30. 2026-09-06 14:19 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  32. 2026-09-06 04:54 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-09-05 23:51 UTCEG score recompute
  34. 2026-09-05 23:51 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  36. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  37. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  38. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  39. 2026-08-31 00:12 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-08-30 20:32 UTCEG score recompute
  41. 2026-08-30 20:32 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  43. 2026-08-30 16:51 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-08-30 11:22 UTCEG score recompute
  45. 2026-08-30 11:22 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  47. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  48. 2026-08-28 02:46 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-08-27 22:14 UTCEG score recompute
  50. 2026-08-27 22:14 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  52. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  53. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  54. 2026-08-25 13:41 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-08-25 04:26 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-08-25 00:42 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-08-24 20:55 UTCEG score recompute
  58. 2026-08-24 20:55 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-08-24 13:56 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-08-24 10:15 UTCEG score recompute
  61. 2026-08-24 10:15 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-08-24 04:55 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-08-24 01:12 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-08-23 21:31 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-08-23 17:50 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-08-23 14:09 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-08-23 10:26 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-08-23 06:27 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-08-23 02:46 UTCEG score recompute
  70. 2026-08-23 02:46 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  72. 2026-08-22 23:04 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-08-22 19:23 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-08-22 13:34 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-08-22 09:49 UTCGHSA enrichmentGHSA-q3h2-6968-258w · GitHub severity CRITICAL · GitHub CVSS 9.8

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58466?
CVE-2026-58466 is a critical-severity vulnerability; its CVE record was published on July 2, 2026. AutoBangumi before 3.2.8 contains a hard-coded default credentials vulnerability that allows unauthenticated attackers to authenticate as the administrator by using the publicly known default credentials seeded at startup via adddefaultuser() in the database user module when the users table is…
When was CVE-2026-58466 made public?
CVE-2026-58466 was made public on June 9, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 2, 2026. EchelonGraph's copy of the record carries a last-modified date of July 14, 2026; the record at its source may have been updated since.
Is CVE-2026-58466 actively exploited?
CVE-2026-58466 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58466?
CVE-2026-58466 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58466?
A fix for CVE-2026-58466 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-58466 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-58466?

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

Book a Demo →Browse All CVEs