Repository navigation
Replies: 1 comment 1 reply
|
I agree. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Scanners are flagging CVE-2026-122146 (fflate ≤ 0.8.3, high) against projects using react-pdf, via:
The CVE is only in fflate's
unzipSync/unzip(ZIP extraction): the output buffer is allocated from the uncompressed size declared in the archive, without a bound. From checking the published code I believe react-pdf is not affected / not reachable, and I'd like to confirm that with you so others triaging the same finding have an answer to point at.What I found (on
@react-pdf/renderer@4.9.0):zlibSyncfrom fflate (PDF-stream compression), and only in the browser build; the Node build uses nativezlib.unzlib(zlib inflate for PNG image data).unzipSync/unzip. A production browser bundle of@react-pdf/renderercontains nounzipSyncand not the ZIP end-of-central-directory signature0x06054b50thatunzipSyncscans for — it's tree-shaken out.pdfkit/js/pdfkit.standalone.jscontains a bundled fflate copy includingunzipSync, but it isn't in pdfkit'sexportsmap and react-pdf never imports it, so it's never loaded.Anyone can check the import surface:
The only named imports are
zlibSync(pdfkit) andunzlib(png-js).pdfkit.standalone.jsalso shows up — it bundles a full fflate copy incl.unzipSync— but it's not exposed via pdfkit'sexportsand isn't loaded by react-pdf.Question: can you confirm this assessment? A short note in the docs/README (or a VEX statement) would help everyone who has to justify the finding to a scanner.
Caveats: I only checked version 4.9.0.
All reactions