This checker covers only CVE-2026-96889, also identified as GHSA-wq5f-xc86-pv6w. The Sharp maintainer advisory and GitHub advisory record were reviewed on 2026-10-24. The enabled source-linked rule is in snapshot.json; the original research metadata remains recorded in advisory.json.
The maintainer identifies Sharp versions below 0.35.5 and recommends its official prebuilt binaries at 0.35.5 or later, which include librsvg 2.63.2. The advisory database header lists 0.35.5 as patched; its description agrees with the maintainer's remediation. We use the maintainer's explicit threshold. The checker limits comparison to stable Sharp 0.x versions through 0.35.x, leaving future release lines unknown rather than extrapolating a dated snapshot.
Custom and global linkage require a separate decision. A fixed Sharp package can still select an independently installed native library. In global mode only independently supplied upstream librsvg 2.63.2 or a later patch in 2.63.x establishes reported remediation. The advisory gives no separate librsvg affected-version introduction range, so an older global native library stays unknown requiring vendor review. The tool does not invent that range or verify backports. Unknown provenance, vendor/custom builds, qualifiers and conflicting observations remain unknown. A reported fix is never a patch attestation.
The advisory describes possible RCE under runtime conditions on glibc Linux and identifies two workarounds: blocking the SVG loader and running a Node executable compiled with PIE. The checker records these dimensions separately. Effective SVG blocking is a decoder mitigation; PIE mitigates the documented RCE condition while other impact from the memory bug may remain. Neither is treated as a fixed library. No assumption about PIE is derived from a Node version, package source, platform or a vendor's usual build policy.
An operator must establish the input path and effective process configuration independently. Merely finding a block call in source would not show that it applies before all image decoding, and the optional source scanner reports only separate lexical candidates. It accepts controlled observations without executing application code. Missing libc or PIE remains unknown; absent runtime conditions do not prove that the library memory bug is absent. All local reachability and exploitability remain not_tested, including when every reported condition is present.
Use build records, native linkage evidence and documented vendor patch provenance from the deployment being assessed. Keep conflicting evidence together; do not delete it or relabel a build to obtain a fixed result. Consult current upstream/vendor guidance, rebuild and redeploy as appropriate, and verify the effective deployed process separately. There is no public-website mode because ordinary response metadata cannot answer these questions.
The 2026-10-25 adapters emit separate unknown records: neither an ELF layout hint nor a lexical block call is an established runtime precondition or mitigation. Metadata package versions do not attest library selection or provenance. See the reference for exact format coverage and bounds.
For explicit version observations, each component's exported evidence preserves all distinct accepted exact values, including conflicts. Only validated stable version strings are retained, never malformed or qualified raw text. This makes distinct conflicts reproducible while keeping the selected version null and the assessment unknown; it does not establish which version is deployed.