Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

GHSA-xg43-5579-qw6v

MEDIUMFix: adawolfa/isdoc@02a1012

GHSA-xg43-5579-qw6v is a medium-severity (CVSS 6.5) remote code execution vulnerability in adawolfa/isdoc. O3 Security confirms whether GHSA-xg43-5579-qw6v is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

adawolfa/isdoc: Uncontrolled resource consumption (decompression bomb) when reading untrusted ISDOCX or PDF files

Published
Jul 15, 2026
Updated
Sep 10, 2026
Affected
4 pkgs
Patched
3 / 4
Exploits
None indexed
Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

4 pkgs affected
🐘adawolfa/isdoc🐘adawolfa/isdoc🐘adawolfa/isdoc🐘adawolfa/isdoc

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

adawolfa/isdoc reads ISDOC invoices from ISDOCX (ZIP) archives and from PDF files with embedded ISDOC documents and supplements. Affected versions inflate ZIP entries and read embedded files without validating their uncompressed size, so a small crafted file can amplify into gigabytes:

  • ISDOCX decompression bombgetFromName() inflates the ISDOC document and binary supplements with no size cap.
  • saveTo() disk-fill — the supplement copy loop writes inflated bytes to disk with no running byte budget, so a bomb can exhaust disk even if the central-directory size is under-reported.
  • PDF embedded files — an embedded file whose declared Length is enormous is read and digested with no upper bound.

Exploitation requires the application to parse an attacker-supplied .isdocx or .pdf (the typical use is generating files or parsing files from trusted vendors, so a user must be induced to process a malicious file). When that happens the process can be driven to exhaust memory or disk, causing denial of service. There is no confidentiality or integrity impact — availability only.

Patches

Fixed in 1.4.3, 1.5.1, 1.6.1 and 2.0.0. The readers now:

  • read the uncompressed size from the ZIP central directory (statName()) and reject entries over a cap before inflating — 256 KB (DocumentSizeLimit) for the ISDOC document, 32 MB (SizeLimit) for supplements;
  • enforce a running byte budget in saveTo() and unlink the partial file on overflow;
  • reject PDF-embedded files whose declared Length exceeds 256 MB before reading or digesting them.

New exceptions ReaderException::zipEntryTooLarge(), SupplementException::supplementTooLarge() and ReaderException::pdfSupplementTooLarge() surface the rejection.

Unsupported versions

Versions before 1.4.0 (the 1.0–1.3 lines) are also affected and will not receive a fix, because they target end-of-life PHP. Users on those lines should upgrade to a maintained release — 1.4.3, 1.5.1, 1.6.1, or 2.0.0.

Workarounds

No code-level workaround exists in affected versions; upgrading is the fix. As mitigation, restrict parsing to trusted input, or enforce an external size / decompression limit (validate ZIP entry sizes, cap process memory) before handing files to the library.

Resources

  • Decompression-bomb fix: commit 935fb2a (backported, released as 1.4.3 / 1.5.1 / 1.6.1) and 02a1012 (master, released as 2.0.0).
  • CWE-409 (Improper Handling of Highly Compressed Data), CWE-400 (Uncontrolled Resource Consumption).

Affected Packages

4 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistadawolfa/isdoc1.6.0&&< 1.6.11.6.1
🐘Packagistadawolfa/isdoc1.5.0&&< 1.5.11.5.1
🐘Packagistadawolfa/isdoc1.4.0&&< 1.4.31.4.3
🐘Packagistadawolfa/isdocall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for adawolfa/isdoc. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update adawolfa/isdoc to 1.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xg43-5579-qw6v is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-xg43-5579-qw6v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-xg43-5579-qw6v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact `adawolfa/isdoc` reads ISDOC invoices from ISDOCX (ZIP) archives and from PDF files with embedded ISDOC documents and supplements. Affected versions inflate ZIP entries and read embedded files **without validating their uncompressed size**, so a small crafted file can amplify into gigabytes: - **ISDOCX decompression bomb** — `getFromName()` inflates the ISDOC document and binary supplements with no size cap. - **`saveTo()` disk-fill** — the supplement copy loop writes inflated bytes to disk with no running byte budget, so a bomb can exhaust disk even if the central-directory size
O3 Security · Impact-Aware SCA

Is GHSA-xg43-5579-qw6v in your dependencies?

O3 detects GHSA-xg43-5579-qw6v across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-xg43-5579-qw6v: adawolfa/isdoc… | O3 Security