Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessFetch hardcoded APP_SECRET from public repo
-
DeliveryObtain target bcrypt hash or intercept any REMEMBERME cookie
-
ExploitRecompute HMAC-SHA256 over forged payload
-
ExecutionSubmit forged cookie to Part-DB
-
ImpactGain authenticated admin session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Credential externalization
MITRE ATT&CK
2 techniques across 2 tactics: Persistence, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Affected deployments are default installations of the official jbtronics/part-db1 Docker image at v2.12.0 or earlier where the operator has NOT overridden APP_SECRET in .env.local or the docker-compose environment section - the entrypoint never randomizes it, so the committed value stays active. Exploitation additionally requires ONE of: (variant 1) possession of the target user's bcrypt password hash, obtainable only through a separate issue such as a DB dump or SQL injection, which the vendor notes is 'not obtainable without another security issue'; or (variant 2) interception of any valid REMEMBERME cookie from any logged-in user, via logged XSS or network interception, since the fieldsHash is embedded in cleartext in the cookie's last 44 characters. Key limiter: instances where the administrator set a custom random APP_SECRET are NOT exploitable; there is no user-interaction or privilege requirement on the target itself. |
| Impact | This is a genuine authentication-bypass flaw (CWE-798, hardcoded secret) but its real-world priority is moderate, consistent with the vuln.today 'this_month' label and the vendor's own MEDIUM rating of this specific issue. The supplied CVSS vector (CVSS:3.1/AV:L/AC:L/PR:H/UI:N, 6.3) conflicts with the description and GHSA advisory: the vector claims local access and high privileges, yet the described attack is a remotely submitted forged remember-me cookie requiring no credentials on the target - these signals are contradictory and the official AV:L/PR:H appears to understate the network exploitability. The true limiting factor is not local access but a precondition: variant 1 (offline forgery) needs the victim's bcrypt hash, obtainable only via a separate flaw such as a DB dump or SQL injection, and variant 2 (cookie extension) needs an intercepted valid REMEMBERME cookie (via XSS or network interception). The GHSA advisory contains functional, live-validated proof-of-concept code for both variants against a default Docker v2.12.0 deployment, which raises practical risk above the raw score. No CISA KEV listing and no EPSS score were provided; there is no evidence of active in-the-wild exploitation. Net: a real, broadly-applicable weakness in default Docker installs that should be patched promptly, but gated by a prerequisite (hash or cookie) that keeps it from being trivial drive-by unauthenticated compromise. |
| Exploit ScenarioDerived | An attacker reads the hardcoded APP_SECRET (a03498528f5a5fc089273ec9ae5b2849) straight from the public Part-DB repository, then either obtains the admin's bcrypt hash from a leaked DB backup, or intercepts any logged-in user's REMEMBERME cookie whose fieldsHash is embedded in cleartext. Using the known secret they recompute a valid HMAC-SHA256 signature for the admin username with a decade-long expiry and submit it as a cookie, gaining a fully authenticated admin session without a password. The GHSA advisory includes working PoC code for both paths and states both were live-validated against a default Docker deployment of v2.12.0. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 23, 2026
Forged remember-me cookies in Part-DB allow unauthenticated remote attackers who meet one prerequisite to authenticate as arbitrary users, including admin, on default Docker deployments that retain the bundled APP_SECRET. The flaw affects Part-DB Server through 2.12.0 and the official jbtronics/part-db1 image; exploitation requires either the target user's bcrypt password hash or interception of any valid REMEMBERME cookie, so deployments with a custom random APP_SECRET are not exposed. Version 2.12.1 fixes the issue and the GHSA advisory includes proof-of-concept scripts with live validation, but there is no CISA KEV entry and the vendor rates this specific issue MEDIUM.
RemediationAI
Upgrade to Part-DB 2.12.1, the vendor-released patch. After upgrading, generate a new random APP_SECRET with openssl rand -hex 32 and set it in .env.local or the environment section of docker-compose.yaml; rotating the secret invalidates existing remember-me cookies, so users will need to re-authenticate. For deployments that cannot immediately upgrade, override APP_SECRET with a unique random value as the primary mitigation, which removes the public-secret forgery path, and invalidate existing REMEMBERME cookies/sessions; this does not address other fixes in 2.12.1, including the separate critical phar upload issue noted in the release. See https://github.com/Part-DB/Part-DB-server/security/advisories/GHSA-99pw-2v29-v4wc and https://github.com/Part-DB/Part-DB-server/releases/tag/v2.12.1.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-798 describes the root cause: the repository's committed .env file contains APP_SECRET=a03498528f5a5fc089273ec9ae5b2849, and the Docker entrypoint only performs migrations and ownership changes rather than generating a random secret. Symfony maps APP_SECRET to kernel.secret, and the remember_me configuration uses it as the HMAC key. SignatureHasher derives a fieldsHash from the user's bcrypt password hash and then computes HMAC-SHA256 over fieldsHash:expires:username; the final REMEMBERME cookie appends fieldsHash in cleartext. An attacker who knows the public secret can forge a cookie for any username when they also know the bcrypt hash, or can extend an intercepted cookie for any user because the cleartext fieldsHash remains reusable. Deployments where the administrator has set a custom random APP_SECRET are not exploitable, and the vendor notes the full forgery variant cannot be performed without another security issue that exposes a password hash.
Know when Docker gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L
Forged cookie is submitted remotely so AV:N and PR:N; success needs the victim's bcrypt hash or an intercepted cookie, an attacker-uncontrolled precondition, so AC:H.
Primary rating from Vendor (github).
CVSS VectorVendor: github
Lifecycle Timeline
1DescriptionCVE.org
Part-DB is an open source inventory management system for electronic components. Prior to version 2.12.1, the file .env committed in the Part-DB repository contains a fixed value for APP_SECRET (a03498528f5a5fc089273ec9ae5b2849). The official Docker image jbtronics/part-db1 does not override or randomize this value at container start-up. Because Symfony uses APP_SECRET (via kernel.secret) as the HMAC key for signing remember-me cookies, any attacker who knows the secret -- or fetches it from the public repository -- can forge an arbitrary-user remember-me cookie and gain a fully authenticated session with no credentials required. This issue has been patched in version 2.12.1.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
An issue was discovered in Appsmith before 1.52. Rated critical severity (CVSS 9.8), this vulnerability is remotely expl
runc through version 1.0-rc6 (used in Docker before 18.09.2) contains a container escape vulnerability that allows attac
Netmaker makes networks with WireGuard. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no a
Unauthenticated remote code execution in Marimo ≤0.20.4 allows attackers to execute arbitrary system commands via the `/
The News & Blog Designer Pack - WordPress Blog Plugin - (Blog Post Grid, Blog Post Slider, Blog Post Carousel, Blog Post
Path traversal in JFrog Artifactory (CWE-22) enables an authenticated low-privilege user to write data outside the inten
Docker 1.3.2 allows remote attackers to execute arbitrary code with root privileges via a crafted (1) image or (2) build
Remote code execution in Gogs through 0.14.2 allows authenticated users (and unauthenticated attackers on default-config
Unauthenticated remote command injection in SGWBOX N3 firmware 2.0.25 lets attackers execute arbitrary operating-system
Remote code execution in Flowise before 3.1.2 allows any authenticated user (or API caller with chatflow view/update per
Remote code execution in NocoBase Workflow Script Node (npm @nocobase/plugin-workflow-javascript) allows authenticated l
Docker Desktop Community Edition before 2.1.0.1 allows local users to gain privileges by placing a Trojan horse docker-c
EUVD-2026-108575
NVD
CVE.org
EPSS
GitHub
Exploit-DB