dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-55445

CRITICAL · 9.3 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

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 · unedited
Qinglong is a timed task management platform supporting Python3, JavaScript, Shell, and Typescript. Prior to 2.20.1, the init guard middleware in back/loaders/express.ts checks /api/user/init but not /open/user/init, while rewrite('/open/*', '/api/$1') rewrites the whitelisted /open/* path after JWT authentication and the guard have passed; an unauthenticated attacker can send PUT /open/user/init to reset administrator credentials on an initialized instance. This issue is fixed in 2.20.1.

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 confidence

The init guard middleware in back/loaders/express.ts checks /api/user/init but fails to check /open/user/init. A rewrite rule converts /open/* to /api/* after JWT authentication and guard checks pass, allowing unauthenticated attackers to reset administrator credentials via PUT /open/user/init on an already-initialized instance.

MitigationUpgrade Qinglong to version 2.20.1 or later. If immediate patching is not feasible, restrict network-level access to /open/ endpoints and implement additional authentication checks on the init endpoint.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Qinglong version
    Check the installed Qinglong version against the fixed version 2.20.1. Look for version information in the application settings, about page, or container/image metadata.
    Affected if The installed version is lower than 2.20.1 and the application is already initialized.
  2. Verify init guard middleware coverage
    Inspect the init guard middleware in back/loaders/express.ts to confirm whether it only checks /api/user/init but omits /open/user/init from protection.
    Affected if The middleware fails to include /open/user/init in its guard checks.
  3. Confirm rewrite rule configuration
    Examine the web server or proxy configuration to verify that a rewrite rule converts /open/* paths to /api/* paths after the guard middleware executes.
    Affected if A rewrite rule exists that maps /open/user/init to /api/user/init after authentication checks.
  4. Test /open/user/init endpoint accessibility
    Send a PUT request to /open/user/init without authentication credentials to determine if the endpoint accepts requests.
    Affected if The endpoint accepts unauthenticated requests and responds without requiring JWT authentication.
  5. Check network exposure of /open/ endpoints
    Determine if /open/* endpoints are externally accessible or behind proper authentication barriers at the network level.
    Affected if The /open/user/init endpoint is exposed to untrusted networks without additional authentication.

The environment is affected if running a Qinglong version below 2.20.1 where the init guard middleware does not cover /open/user/init, the /open/* to /api/* rewrite occurs after guard checks, and the endpoint is accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Qinglong to version 2.20.1 or later. If immediate patching is not feasible, restrict network-level access to /open/ endpoints and implement additional authentication checks on the init endpoint.

Recommended fix High confidence

2.20.1

  1. Upgrade Qinglong to version 2.20.1 or later to address the authentication bypass vulnerability
  2. After upgrading, verify that the /open/user/init endpoint is now properly protected by the init guard middleware
  3. Confirm that existing administrator credentials remain intact and accessible only to authenticated users

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55445 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55445 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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