CVE-2026-12191
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 · uneditedA vulnerability was found in Comma AI Openpilot 0.11. This issue affects the function pickle.load/pickle.loads of the file selfdrive/modeld/modeld.py of the component Pickle Module. The manipulation results in deserialization. The attack is only possible with local access. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceA deserialization vulnerability exists in Comma AI Openpilot 0.11 where the pickle.load/pickle.loads function in selfdrive/modeld/modeld.py is used unsafely. Python's pickle module is known to allow arbitrary code execution when deserializing untrusted data, as the unpickling process can instantiate arbitrary objects including those with malicious __reduce__ methods.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Locate the vulnerable modeld.py fileFind the file selfdrive/modeld/modeld.py in your openpilot installation directory. On a typical comma device, this would be under /data/openpilot/selfdrive/modeld/modeld.pyAffected if The file exists and contains pickle.load or pickle.loads function calls
-
Inspect pickle deserialization usageOpen selfdrive/modeld/modeld.py and search for instances of pickle.load or pickle.loads. Check if they deserialize data from untrusted sources such as files, network inputs, or message queues without prior validationAffected if pickle.load or pickle.loads is called without cryptographic signature verification or input validation on the data being deserialized
-
Determine if modeld component is activeCheck if the modeld process is running on your device. On comma devices, you can use 'ps -ef | grep modeld' or check system servicesAffected if The modeld service is enabled and running, accepting external data that could be crafted to exploit the deserialization flaw
-
Check openpilot version against available fixesCompare your installed openpilot version to the latest release that may contain a fix. Use 'cd /data/openpilot && git log --oneline -1' or check the version file if availableAffected if Your version predates any security update that replaces unsafe pickle deserialization with safer alternatives like JSON or signed data
You are affected if selfdrive/modeld/modeld.py uses pickle.load/loads on untrusted data and your openpilot version does not include a fix for this deserialization vulnerability
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 dataReplace pickle.load/loads with safe deserialization methods (JSON, msgpack) or ensure pickled data originates only from trusted, integrity-protected sources. Since local access is required, also limit filesystem permissions on any pickled data files.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12191 — 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-12191 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