Cyber & AI intelligence
Briefs indexed3786
Issues37
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-130856 2026-11-17

CVE-2026-130856: Unauthenticated Reinitialization Lets Attackers Take Over 53AIHub Instances

"A critical missing-authentication flaw in 53AIHub before 0.5.5 lets remote, unauthenticated attackers reinitialize an installed instance through the public `POST /api/init` endpoint and take over accounts."

A critical missing-authentication flaw in 53AIHub before 0.5.5 lets remote, unauthenticated attackers reinitialize an installed instance through the public POST /api/init endpoint and take over accounts.

What Is It

CVE-2026-130856 is a missing authentication vulnerability (CWE-306) in 53AI's 53AIHub. The POST /api/init endpoint, which should only work during first-time setup, stays publicly reachable on instances that are already installed. By calling it, an attacker can:

The attacker can then take over accounts and call admin-only API routes. VulnCheck disclosed the issue, and NVD published it on 2026-11-17. The NVD record is currently marked "Deferred."

Why It Matters

VulnCheck rates this flaw 9.8 CRITICAL under CVSS 3.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and 9.3 CRITICAL under CVSS 4.0. The attack works over the network with low complexity. It needs no privileges and no user interaction. Confidentiality, integrity and availability impacts are all rated High.

According to the advisory, an unauthenticated attacker who reaches the exposed POST /api/init endpoint can reset an account's password, grant it the creator role and obtain an access token. That access can then be used to take over accounts and reach admin-only API routes. Any 53AIHub instance reachable from the internet should be treated as high priority.

The supplied data includes no CISA KEV entry, so active exploitation is not confirmed by KEV at this time.

What's Vulnerable

The record's code references point to the route definition in api/router/api.go and the install logic in api/service/enterprise_install.go.

Patch Status

The record lists versions before 0.5.5 as affected, and the references include the 53AIHub v0.5.5 release tag. Upgrade to 53AIHub 0.5.5 or later. The references also include a related upstream commit and GitHub issue #110. Because there is no KEV entry, there is no CISA-mandated required action or due date. Until upgraded instances are confirmed, organizations running 53AIHub should treat exposed instances as at risk of compromise.

Sources