Skip to main content
Mallory
UnratedVulnerability

CVE-2026-4047: Authentication Bypass via Case-Insensitive /api/ Path Handling in Qinglong

Updated 7 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildReported3 exploitation records in Mallory
IdentifiersCVE-2026-4047CWE-288

CVE-2026-4047 is an authentication bypass vulnerability in Qinglong affecting version 2.20.1 and earlier. The flaw is caused by a mismatch between Qinglong’s authentication middleware and Express.js routing behavior: the authentication check treats protected paths such as /api/ as case-sensitive, while the router matches paths case-insensitively. As a result, an unauthenticated attacker can send requests to altered path variants such as /aPi/... to bypass authentication and reach endpoints intended to be protected. According to the provided reporting, this issue was documented in GitHub Issue #2934 and was observed to enable direct remote code execution by reaching protected functionality without first resetting credentials.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated remote attacker to bypass access controls on protected Qinglong API endpoints. Based on the provided context, this can lead directly to remote code execution on vulnerable Qinglong instances and was actively exploited in the wild to modify config.sh and deploy a hidden cryptominer (.fullgc), resulting in severe CPU exhaustion and full compromise of exposed panels.

Mitigation

If you can’t patch tonight, do this now.

Until patched, restrict access to Qinglong panels so they are not publicly exposed to the internet, for example by placing them behind a secure VPN or otherwise limiting trusted source access. Monitor for and investigate unauthorized access to protected /api/ functionality via mixed-case path variants such as /aPi/. Audit compromised or potentially exposed systems for persistence or payloads mentioned in the reporting, including hidden .fullgc files/processes and unauthorized modifications to config.sh.

Remediation

Patch, then assume compromise.

Upgrade Qinglong to a version containing the effective fix referenced in the provided context as PR #2941. The initial mitigation that relied on filtering malicious inputs was reported as insufficient because it did not correct the underlying access-control flaw. Remediation should therefore ensure the authentication middleware logic is corrected so that authorization decisions are consistent with actual router path matching behavior. Operators should also update affected Docker containers if Qinglong is deployed via Docker.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-4047 exploited in the wild?
Yes. As of May 1, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-4047?
As of May 1, 2026, Mallory has found no public exploit for CVE-2026-4047.
Is there a patch for CVE-2026-4047?
Upgrade Qinglong to a version containing the effective fix referenced in the provided context as PR #2941. The initial mitigation that relied on filtering malicious inputs was reported as insufficient because it did not correct the underlying access-control flaw.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.