Ad · Leaderboard 728×90

CVE-2026-110616

8.1High

Published 14 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash

8.1High
Attack vector
Network
Complexity
High
Privileges needed
None
User interaction
None
Impact
Full C/I/A compromise
Weakness
CWE-306

Impact

Unauthenticated attackers with network access can fully take over NullHub management by hitting the /api/* endpoints. They can hijack agent instances, rewrite provider credentials, and control MCP servers or cron jobs.

Root cause

The auth_token configuration field defaults to null and is never assigned, allowing requests without Authorization or Origin headers to bypass authentication entirely.

Affected systems

NullHub through 2026.5.29

CVSS v3.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Fix & remediation

No fixed release is listed yet. Block external access to the NullHub port at the firewall or bind the service strictly to the loopback interface (127.0.0.1) so it cannot be reached over the network.

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

NullHub through 2026.5.29 contains a missing authentication vulnerability that allows unauthenticated attackers to access the /api/* management API because the auth_token field defaults to null and is never assigned. Attackers sending requests without Authorization or Origin headers to non-loopback listeners can control agent instances, rewrite configurations including provider credentials, and manage cron jobs and MCP servers.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-110616

Ad · Sticky 320×50 / 728×90