Authentication Bypass in @whyour/qinglong (CVE-2026-55445)
Summary
Authentication bypass in @whyour/qinglong (CVE-2026-55445). Risk of unauthorized operations or information disclosure. Exploitable via PUT /open/user/init. Mitigation: upgrade to 2.20.1 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55445 has been found in @whyour/qinglong.
Attackers can target a specific entry point like PUT /open/user/init over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @whyour/qinglong to 2.20.1 or later.
If unsure, ask your IT team or search "@whyour/qinglong CVE-2026-55445" on the vendor's site.
CVE-2026-55445 (@whyour/qinglong) — CWE-287
Attack surface: PUT /open/user/init / PUT /api/user/init
Patched: 2.20.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in @whyour/qinglong. Attackers reach the vulnerable code path via PUT /open/user/init.
Check the vendor advisory for the affected versions of @whyour/qinglong. Attack surface: PUT /open/user/init / PUT /api/user/init.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.20.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PUT /open/user/init requests with malformed payloads or SQL meta-characters. Run grep -r '@whyour/qinglong' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@whyour/qinglong' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@whyour/qinglongを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'PUT /open/user/init' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PUT /open/user/initへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade @whyour/qinglong to 2.20.1ステージング環境で 2.20.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against PUT /open/user/init on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com