CVE-2026-36576
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 · uneditedAn OS command injection vulnerability in the app.py component of openlabs docker-wkhtmltopdf-aas up to commit 9f50579 allows attackers to execute arbitrary commands via a crafted POST request.
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 confidenceOS command injection vulnerability in docker-wkhtmltopdf-aas allows remote attackers to execute arbitrary OS commands through unsanitized input in POST requests to the app.py component, achieving maximum severity (CVSS 9.8) due to the critical nature of command injection.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if docker-wkhtmltopdf-aas is runningCheck for running containers or processes named 'docker-wkhtmltopdf-aas' or 'wkhtmltopdf-aas' using 'docker ps' or process listing toolsAffected if The container or service is active and accessible
-
Locate and inspect app.py for command execution patternsFind the app.py file in the container or installation directory and examine how PDF conversion commands are constructed - look for use of os.system(), subprocess.call(), or similar shell execution methods with unsanitized user inputAffected if app.py uses shell command invocation (e.g., subprocess with shell=True) and processes user-supplied input without sanitization
-
Verify if input validation is implementedSearch app.py for input validation functions, allowlists, or parameterized execution methods - check for patterns like input validation routines, whitelist checks, or use of shlex.quote() or equivalentAffected if No input validation, sanitization, or allowlist-based filtering is present before command construction
-
Determine if the web interface is exposedCheck if the application is bound to a network interface (e.g., listen address 0.0.0.0 vs 127.0.0.1) and accessible via HTTP POST requests on the conversion endpointAffected if The service is accessible over the network and accepts POST requests
-
Compare installed version to the patched commitCheck the git commit history or version tag of the installed codebase against commit 9f50579 - if the installed version is before this commit, it is likely vulnerableAffected if The installed version is prior to commit 9f50579 or does not include the input sanitization fix
A user is affected if docker-wkhtmltopdf-aas is running, app.py uses shell command execution with unsanitized user input, and the web interface is accessible to attackers.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to a version beyond commit 9f50579 that includes proper input sanitization or implement input validation and parameterized command execution in app.py to prevent shell command injection.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36576 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-36576 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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