CVE-2026-38422
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 · uneditedBuffer Overflow vulnerability in arendst Tasmota v.15.3.0.3 and before allows a remote attacker to execute arbitrary code via the tasmota/tasmota_xdrv_driver/xdrv_10_scripter.ino, fetch_jpg() function.
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 confidenceA buffer overflow vulnerability exists in the fetch_jpg() function within the xdrv_10_scripter.ino driver of Tasmota firmware versions 15.3.0.3 and prior. The vulnerability allows remote attackers to execute arbitrary code via malformed JPEG fetch requests, potentially compromising the entire IoT device running the firmware.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Confirm Tasmota firmware is runningAccess the device web interface or send a GET request to the device IP, or use the Tasmota console and run command 'Status' to see the firmware informationAffected if The device is running Tasmota firmware - this is required for the vulnerability to apply
-
Check Tasmota firmware versionIn the Tasmota console, run command 'Status 1' or check the web UI footer which displays the version number (e.g., 15.3.0.3, 15.2.1, etc.)Affected if Version is 15.3.0.3 or any earlier version - versions 15.3.0.3 and prior are affected
-
Verify scripter driver is loadedIn the Tasmota console, run command 'Modules' or 'Driver' to see which drivers are active. The vulnerability is in xdrv_10_scripter.ino driverAffected if The scripter driver (xdrv_10_scripter) appears in the loaded modules list - the flaw only applies when this driver is enabled
-
Check if scripter script functionality is configuredIn the Tasmota console, run command 'Script' to display any active script configuration that may invoke the fetch_jpg() functionAffected if A script is configured that uses the fetch_jpg() function - this is the attack vector for the buffer overflow
A user is affected if the device runs Tasmota firmware version 15.3.0.3 or earlier, has the scripter driver enabled, and has a script configured that utilizes the fetch_jpg() function to process JPEG requests.
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 Tasmota firmware to a version beyond 15.3.0.3 that includes the patch for this vulnerability. If no patched version is available, restrict network access to affected devices and disable the scripter functionality if not required.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,640.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38422 — 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-38422 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