UEFI Firmware Parser has a stack out-of-bounds write in tiano decompressor MakeTable
CVE-2026-54333GHSA-2689-5p89-6j3j
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI uefi-firmware
- Affected
- <= 1.12
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-2689-5p89-6j3j lists affected ranges: PyPI uefi-firmware >=0 <=1.12
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-2689-5p89-6j3j lists affected ranges: PyPI uefi-firmware >=0 <=1.12
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2026-54333: 0.80% estimated exploitation activity in the next 30 days; percentile 56.68 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
uefi-firmware contains a stack out-of-bounds write vulnerability in the native tiano/EFI decompressor. in uefifirmware/compression/Tiano/Decompress.c, MakeTable() does not validate that bit-length values read from the compressed bitstream are within the expected range (0..16). a crafted firmware blob can supply bit lengths greater than 16, causing out-of-bounds writes to the stack-allocated Count[17] array and related decode tables. reachability is through the normal parsing path: CompressedSection.process() - eficompressor.TianoDecompress() - TianoDecompress() - ReadPTLen() - MakeTable(). Minimum impact is a deterministic crash; depending on build/runtime details, the stack memory corruption may be exploitable for code execution in the context of the parsing process. this project shipped its own copy of the decompressor without the upstream EDK2 hardening for this bug class. References: - PR: <https://github.com/theopolis/uefi-firmware-parser/pull/145 - fix commit:…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-2689-5p89-6j3j
- Revision 2 · amended ·
Amended from osv record GHSA-2689-5p89-6j3j
- Revision 1 · created ·
Published from ghsa record GHSA-2689-5p89-6j3j
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-54333 Advisory: UEFI Firmware Parser has a stack out-of-bounds write in tiano decompressor MakeTable IDs: CVE-2026-54333, GHSA-2689-5p89-6j3j Record: https://patchnext.com/advisories/cve-2026-54333 (revision 3, source checked 26 Oct 2026, 13:46 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI uefi-firmware: affected <= 1.12 ## Suggested inspection (read-only) - `python -m pip show uefi-firmware`: prints the installed version. Run with the environment that serves production active. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on uefi-firmware. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-2689-5p89-6j3j (GitHub-reviewed advisory GHSA-2689-5p89-6j3j lists affected ranges: PyPI uefi-firmware >=0 <=1.12) - Verified: https://osv.dev/vulnerability/GHSA-2689-5p89-6j3j (OSV record GHSA-2689-5p89-6j3j lists affected ranges: PyPI uefi-firmware >=0 <=1.12) Commands are suggestions: review each one before running it.
Loading voting…