NPM · SEPTEMBER 2026 · EARLY WARNING

Authentication Bypass in _account_log Function: Early Warning

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
Severity
CRITICAL
CVSS
9.8
Affected component
cve-2026-27546 (npm)
Patched version
Not yet available
CVE-2026-27546

An authentication bypass vulnerability in the _account_log function has been reported. This vulnerability allows an unauthenticated remote attacker to log in as an admin.

What happened

An early warning has been issued regarding a critical vulnerability in the _account_log function. This vulnerability, tracked as CVE-2026-27546, allows an unauthenticated remote attacker to bypass authentication and log in as an admin. The vulnerability has a CVSS score of 9.8, indicating a critical severity level. The issue was first flagged on 2026-09-16T08:16:36.850000+00:00.

The vulnerability is present in the npm package cve-2026-27546. However, no authoritative version range has been published yet. It is crucial for users of this package to assess their exposure and take immediate action to mitigate the risk.

What to do about it

How 0Day would have caught this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If cve-2026-27546 is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Frequently asked questions

Am I affected?

If you are using the cve-2026-27546 npm package, you may be affected. However, no authoritative version range has been published yet. It is recommended to assess your exposure and take appropriate action.

What should I do right now?

Pin to a non-vulnerable version of the cve-2026-27546 npm package if possible. Monitor the primary sources for updates on a patch. Rotate any secrets in affected environments as a precautionary measure.

Is there an official fix available?

No official fix has been published yet. Monitor the primary sources for updates on any available patches.

Sources

Join the 0Day waitlist →

← Back to all threats