CVE-2026-58466
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAutoBangumi 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAutoBangumi before 3.2.8 creates hard-coded default administrator credentials via add_default_user() when the users table is empty. Attackers with knowledge of these publicly seeded credentials can authenticate to the login endpoint and gain full administrative control over RSS feed configurations, downloader settings, and all authenticated API endpoints.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed AutoBangumi versionCheck the application version file, Docker image tag, or running service version (e.g., docker ps, pip show autobangumi, or the web UI about page)Affected if version is lower than 3.2.8 (e.g., 3.2.7, 3.2.6, etc.)
-
Inspect database users table stateAccess the SQLite/database file used by AutoBangumi and query the users table: SELECT * FROM users; or check if the table is emptyAffected if the users table exists but contains no rows (is empty), or contains a user account created by default with predictable credentials
-
Verify default credential presenceExamine the database user records for accounts with default usernames (commonly 'admin', 'root', or similar) that may have been auto-created on first startup when no users existedAffected if a default administrator account exists that was auto-generated on initial setup
-
Check login endpoint accessibilityConfirm the AutoBangumi web interface login endpoint is network-accessible (e.g., curl http://target:7899/login or similar port the service runs on)Affected if the login endpoint is exposed to untrusted networks without authentication barriers
You are affected if AutoBangumi version is below 3.2.8 AND the users table is empty or contains a default auto-generated administrator account, especially if the login endpoint is network-accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to version 3.2.8 or later which should remove the hard-coded default credential seeding. Verify that any existing deployment does not have default credentials in use and force a credential reset if the system was previously vulnerable.
AutoBangumi version 3.2.8
- Back up your current AutoBangumi installation and database before upgrading.
- Upgrade AutoBangumi to version 3.2.8 or later where the hard-coded default credentials vulnerability is fixed.
- After upgrading, verify that the add_default_user() function no longer seeds hard-coded credentials in an insecure manner.
- If you previously used default credentials or suspect compromise, create new administrator accounts with strong, unique passwords and delete any unauthorized accounts.
- Review application logs for any unauthorized access attempts using default credentials.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58466 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-58466 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data