synthetic-bundle · Sharp (bundled librsvg)
precondition_present
Reported version: 0.35.4 · Rule: CVE-2026-96889 · Exploitability: not_tested
For official bundled binaries, upgrade Sharp to 0.35.5 or a later supported patched release. For a global library, independently verify the selected librsvg and apply the upstream 2.63.2 fix or a documented vendor fix. Rebuild/redeploy and verify the actual linkage. Effective VipsForeignLoadSvg blocking and Node PIE are separate mitigations; neither attests the library patch set.
- The reported official Sharp bundle is below 0.35.5.
- Version, platform, libc, effective mitigation and input-path observations are operator claims; local exploitability remains not_tested.
- A mitigated configuration preserves an affected library/package assessment and does not establish safety or absence of prior compromise.
Evidence and assessment dimensions
- version: present — The reported official Sharp bundle is below 0.35.5.
- inventory: present — Operator-reported library selection: bundled; linkage is not independently verified.
- inventory: present — Sharp version observation: 0.35.4.
- inventory: unknown — librsvg version observation: missing, qualified or conflicting.
- configuration: present — Reported platform: linux; reported libc: glibc. Other platforms do not establish that the underlying memory bug is absent.
- configuration: present — Reported effective SVG decoder state: enabled. A blocked claim must cover VipsForeignLoadSvg in the deployed process.
- configuration: present — Reported Node executable PIE state: disabled. No binary inspection is performed.
- configuration: present — Operator-reviewed untrusted SVG input path: present. No data-flow or reachability test is performed.
{
+CompleteTech LLCSecurity evidence report
sharp-rsvg-rce-check 0.2.0 · rules verified 2026-10-24
Completed assessmentLocal exploitability is not tested. Version, configuration, candidate source patterns and external exploitation reports are separate evidence.
precondition_present: 1 · mitigated_configuration: 1 · fixed_version_reported: 1 · unknown: 1
- Offline supplied evidence and explicitly selected metadata only; library selection, deployed versions, provenance and effective mitigations are not independently attested.
- No network requests, application execution, image decoding, exploitation, reachability test or compromise detection is performed.
- The Sharp comparison covers exact stable 0.0-0.35 versions. Global librsvg has a documented remediation build, not a published independent affected-version range; only stable 2.63.2+ within 2.63 is accepted as reported remediation.
- PIE is an RCE mitigation, not a library patch or a guarantee against other memory-corruption impact. Unknown libc or PIE remains unknown.
synthetic-bundle · Sharp (bundled librsvg)
precondition_present
Reported version: 0.35.4 · Rule: CVE-2026-96889 · Exploitability: not_tested
For official bundled binaries, upgrade Sharp to 0.35.5 or a later supported patched release. For a global library, independently verify the selected librsvg and apply the upstream 2.63.2 fix or a documented vendor fix. Rebuild/redeploy and verify the actual linkage. Effective VipsForeignLoadSvg blocking and Node PIE are separate mitigations; neither attests the library patch set.
- The reported official Sharp bundle is below 0.35.5.
- Version, platform, libc, effective mitigation and input-path observations are operator claims; local exploitability remains not_tested.
- A mitigated configuration preserves an affected library/package assessment and does not establish safety or absence of prior compromise.
Evidence and assessment dimensions
- version: present — The reported official Sharp bundle is below 0.35.5.
- inventory: present — Operator-reported library selection: bundled; linkage is not independently verified.
- inventory: present — Sharp version observation: 0.35.4. Accepted exact observations: 0.35.4.
- inventory: unknown — librsvg version observation: missing, qualified or conflicting.
- configuration: present — Reported platform: linux; reported libc: glibc. Other platforms do not establish that the underlying memory bug is absent.
- configuration: present — Reported effective SVG decoder state: enabled. A blocked claim must cover VipsForeignLoadSvg in the deployed process.
- configuration: present — Reported Node executable PIE state: disabled. This operator claim is not inferred from optional binary metadata hints.
- configuration: present — Operator-reviewed untrusted SVG input path: present. No data-flow or reachability test is performed.
{
"confidence": "low",
"mitigation": {
"evidence_ids": [],
@@ -64,7 +64,7 @@
}
},
"version_assessment": "affected"
-}synthetic-pie-mitigation · Sharp (bundled librsvg)
mitigated_configuration
Reported version: 0.35.4 · Rule: CVE-2026-96889 · Exploitability: not_tested
For official bundled binaries, upgrade Sharp to 0.35.5 or a later supported patched release. For a global library, independently verify the selected librsvg and apply the upstream 2.63.2 fix or a documented vendor fix. Rebuild/redeploy and verify the actual linkage. Effective VipsForeignLoadSvg blocking and Node PIE are separate mitigations; neither attests the library patch set.
- The reported official Sharp bundle is below 0.35.5.
- Version, platform, libc, effective mitigation and input-path observations are operator claims; local exploitability remains not_tested.
- A mitigated configuration preserves an affected library/package assessment and does not establish safety or absence of prior compromise.
Evidence and assessment dimensions
- version: present — The reported official Sharp bundle is below 0.35.5.
- inventory: present — Operator-reported library selection: bundled; linkage is not independently verified.
- inventory: present — Sharp version observation: 0.35.4.
- inventory: unknown — librsvg version observation: missing, qualified or conflicting.
- configuration: unknown — Reported platform: unknown; reported libc: unknown. Other platforms do not establish that the underlying memory bug is absent.
- configuration: unknown — Reported effective SVG decoder state: unknown. A blocked claim must cover VipsForeignLoadSvg in the deployed process.
- configuration: absent — Reported Node executable PIE state: enabled. No binary inspection is performed.
- configuration: unknown — Operator-reviewed untrusted SVG input path: unknown. No data-flow or reachability test is performed.
- configuration: present — Node PIE is operator-reported; it mitigates the documented RCE condition, not other memory-corruption impacts or library patch state.
{
+}synthetic-pie-mitigation · Sharp (bundled librsvg)
mitigated_configuration
Reported version: 0.35.4 · Rule: CVE-2026-96889 · Exploitability: not_tested
For official bundled binaries, upgrade Sharp to 0.35.5 or a later supported patched release. For a global library, independently verify the selected librsvg and apply the upstream 2.63.2 fix or a documented vendor fix. Rebuild/redeploy and verify the actual linkage. Effective VipsForeignLoadSvg blocking and Node PIE are separate mitigations; neither attests the library patch set.
- The reported official Sharp bundle is below 0.35.5.
- Version, platform, libc, effective mitigation and input-path observations are operator claims; local exploitability remains not_tested.
- A mitigated configuration preserves an affected library/package assessment and does not establish safety or absence of prior compromise.
Evidence and assessment dimensions
- version: present — The reported official Sharp bundle is below 0.35.5.
- inventory: present — Operator-reported library selection: bundled; linkage is not independently verified.
- inventory: present — Sharp version observation: 0.35.4. Accepted exact observations: 0.35.4.
- inventory: unknown — librsvg version observation: missing, qualified or conflicting.
- configuration: unknown — Reported platform: unknown; reported libc: unknown. Other platforms do not establish that the underlying memory bug is absent.
- configuration: unknown — Reported effective SVG decoder state: unknown. A blocked claim must cover VipsForeignLoadSvg in the deployed process.
- configuration: absent — Reported Node executable PIE state: enabled. This operator claim is not inferred from optional binary metadata hints.
- configuration: unknown — Operator-reviewed untrusted SVG input path: unknown. No data-flow or reachability test is performed.
- configuration: present — Node PIE is operator-reported; it mitigates the documented RCE condition, not other memory-corruption impacts or library patch state.
{
"confidence": "low",
"mitigation": {
"evidence_ids": [
@@ -122,7 +122,7 @@
}
},
"version_assessment": "affected"
-}synthetic-global-fixed · librsvg (global, used by Sharp)
fixed_version_reported
Reported version: 2.63.2 · Rule: CVE-2026-96889 · Exploitability: not_tested
For official bundled binaries, upgrade Sharp to 0.35.5 or a later supported patched release. For a global library, independently verify the selected librsvg and apply the upstream 2.63.2 fix or a documented vendor fix. Rebuild/redeploy and verify the actual linkage. Effective VipsForeignLoadSvg blocking and Node PIE are separate mitigations; neither attests the library patch set.
- The independently reported global librsvg meets the documented 2.63.2 remediation build in the reviewed 2.63 line.
- Version, platform, libc, effective mitigation and input-path observations are operator claims; local exploitability remains not_tested.
- A mitigated configuration preserves an affected library/package assessment and does not establish safety or absence of prior compromise.
Evidence and assessment dimensions
- version: present — The independently reported global librsvg meets the documented 2.63.2 remediation build in the reviewed 2.63 line.
- inventory: present — Operator-reported library selection: global; linkage is not independently verified.
- inventory: present — Sharp version observation: 0.35.4.
- inventory: present — librsvg version observation: 2.63.2.
- configuration: unknown — Reported platform: unknown; reported libc: unknown. Other platforms do not establish that the underlying memory bug is absent.
- configuration: unknown — Reported effective SVG decoder state: unknown. A blocked claim must cover VipsForeignLoadSvg in the deployed process.
- configuration: unknown — Reported Node executable PIE state: unknown. No binary inspection is performed.
- configuration: unknown — Operator-reviewed untrusted SVG input path: unknown. No data-flow or reachability test is performed.
{
+}synthetic-global-fixed · librsvg (global, used by Sharp)
fixed_version_reported
Reported version: 2.63.2 · Rule: CVE-2026-96889 · Exploitability: not_tested
For official bundled binaries, upgrade Sharp to 0.35.5 or a later supported patched release. For a global library, independently verify the selected librsvg and apply the upstream 2.63.2 fix or a documented vendor fix. Rebuild/redeploy and verify the actual linkage. Effective VipsForeignLoadSvg blocking and Node PIE are separate mitigations; neither attests the library patch set.
- The independently reported global librsvg meets the documented 2.63.2 remediation build in the reviewed 2.63 line.
- Version, platform, libc, effective mitigation and input-path observations are operator claims; local exploitability remains not_tested.
- A mitigated configuration preserves an affected library/package assessment and does not establish safety or absence of prior compromise.
Evidence and assessment dimensions
- version: present — The independently reported global librsvg meets the documented 2.63.2 remediation build in the reviewed 2.63 line.
- inventory: present — Operator-reported library selection: global; linkage is not independently verified.
- inventory: present — Sharp version observation: 0.35.4. Accepted exact observations: 0.35.4.
- inventory: present — librsvg version observation: 2.63.2. Accepted exact observations: 2.63.2.
- configuration: unknown — Reported platform: unknown; reported libc: unknown. Other platforms do not establish that the underlying memory bug is absent.
- configuration: unknown — Reported effective SVG decoder state: unknown. A blocked claim must cover VipsForeignLoadSvg in the deployed process.
- configuration: unknown — Reported Node executable PIE state: unknown. This operator claim is not inferred from optional binary metadata hints.
- configuration: unknown — Operator-reviewed untrusted SVG input path: unknown. No data-flow or reachability test is performed.
{
"confidence": "low",
"mitigation": {
"evidence_ids": [],
@@ -178,7 +178,7 @@
}
},
"version_assessment": "fixed_reported"
-}synthetic-unknown-linkage · Sharp librsvg selection
unknown
Reported version: unknown · Rule: CVE-2026-96889 · Exploitability: not_tested
For official bundled binaries, upgrade Sharp to 0.35.5 or a later supported patched release. For a global library, independently verify the selected librsvg and apply the upstream 2.63.2 fix or a documented vendor fix. Rebuild/redeploy and verify the actual linkage. Effective VipsForeignLoadSvg blocking and Node PIE are separate mitigations; neither attests the library patch set.
- Library selection is unknown; a patched Sharp package cannot establish the version of a possible global librsvg.
- Version, platform, libc, effective mitigation and input-path observations are operator claims; local exploitability remains not_tested.
- A mitigated configuration preserves an affected library/package assessment and does not establish safety or absence of prior compromise.
Evidence and assessment dimensions
- version: unknown — Library selection is unknown; a patched Sharp package cannot establish the version of a possible global librsvg.
- inventory: unknown — Operator-reported library selection: unknown; linkage is not independently verified.
- inventory: present — Sharp version observation: 0.35.5.
- inventory: unknown — librsvg version observation: missing, qualified or conflicting.
- configuration: unknown — Reported platform: unknown; reported libc: unknown. Other platforms do not establish that the underlying memory bug is absent.
- configuration: unknown — Reported effective SVG decoder state: unknown. A blocked claim must cover VipsForeignLoadSvg in the deployed process.
- configuration: unknown — Reported Node executable PIE state: unknown. No binary inspection is performed.
- configuration: unknown — Operator-reviewed untrusted SVG input path: unknown. No data-flow or reachability test is performed.
{
+}synthetic-unknown-linkage · Sharp librsvg selection
unknown
Reported version: unknown · Rule: CVE-2026-96889 · Exploitability: not_tested
For official bundled binaries, upgrade Sharp to 0.35.5 or a later supported patched release. For a global library, independently verify the selected librsvg and apply the upstream 2.63.2 fix or a documented vendor fix. Rebuild/redeploy and verify the actual linkage. Effective VipsForeignLoadSvg blocking and Node PIE are separate mitigations; neither attests the library patch set.
- Library selection is unknown; a patched Sharp package cannot establish the version of a possible global librsvg.
- Version, platform, libc, effective mitigation and input-path observations are operator claims; local exploitability remains not_tested.
- A mitigated configuration preserves an affected library/package assessment and does not establish safety or absence of prior compromise.
Evidence and assessment dimensions
- version: unknown — Library selection is unknown; a patched Sharp package cannot establish the version of a possible global librsvg.
- inventory: unknown — Operator-reported library selection: unknown; linkage is not independently verified.
- inventory: present — Sharp version observation: 0.35.5. Accepted exact observations: 0.35.5.
- inventory: unknown — librsvg version observation: missing, qualified or conflicting.
- configuration: unknown — Reported platform: unknown; reported libc: unknown. Other platforms do not establish that the underlying memory bug is absent.
- configuration: unknown — Reported effective SVG decoder state: unknown. A blocked claim must cover VipsForeignLoadSvg in the deployed process.
- configuration: unknown — Reported Node executable PIE state: unknown. This operator claim is not inferred from optional binary metadata hints.
- configuration: unknown — Operator-reviewed untrusted SVG input path: unknown. No data-flow or reachability test is performed.
{
"confidence": "unknown",
"mitigation": {
"evidence_ids": [],
diff --git a/sharp_rsvg_rce_check.py b/sharp_rsvg_rce_check.py
index 4887eeb..c264ebc 100644
--- a/sharp_rsvg_rce_check.py
+++ b/sharp_rsvg_rce_check.py
@@ -1013,8 +1013,12 @@ def assess_record(raw):
"detail": "Operator-reported library selection: " + record["library_source"] + "; linkage is not independently verified."}]
for key, label in (("sharp_versions", "Sharp"), ("librsvg_versions", "librsvg")):
value, _, state = version_observation(record[key])
+ accepted = sorted({item for item in record[key] if exact_version(item) is not None})
+ detail = label + " version observation: " + (value if value else "missing, qualified or conflicting") + "."
+ if accepted:
+ detail += " Accepted exact observations: " + ", ".join(accepted) + "."
evidence.append({"id": key.replace("_", "-"), "kind": "inventory", "state": state,
- "detail": label + " version observation: " + (value if value else "missing, qualified or conflicting") + "."})
+ "detail": detail})
platform, libc = record["platform"], record["libc"]
glibc = "absent" if platform == "other" or (platform == "linux" and libc in {"musl", "other"}) else "present" if platform == "linux" and libc == "glibc" else "unknown"
states = {
diff --git a/src/checker.py b/src/checker.py
index 34f4116..0a5c42d 100644
--- a/src/checker.py
+++ b/src/checker.py
@@ -126,8 +126,12 @@ def assess_record(raw):
"detail": "Operator-reported library selection: " + record["library_source"] + "; linkage is not independently verified."}]
for key, label in (("sharp_versions", "Sharp"), ("librsvg_versions", "librsvg")):
value, _, state = version_observation(record[key])
+ accepted = sorted({item for item in record[key] if exact_version(item) is not None})
+ detail = label + " version observation: " + (value if value else "missing, qualified or conflicting") + "."
+ if accepted:
+ detail += " Accepted exact observations: " + ", ".join(accepted) + "."
evidence.append({"id": key.replace("_", "-"), "kind": "inventory", "state": state,
- "detail": label + " version observation: " + (value if value else "missing, qualified or conflicting") + "."})
+ "detail": detail})
platform, libc = record["platform"], record["libc"]
glibc = "absent" if platform == "other" or (platform == "linux" and libc in {"musl", "other"}) else "present" if platform == "linux" and libc == "glibc" else "unknown"
states = {
diff --git a/test_conflict_evidence.py b/test_conflict_evidence.py
new file mode 100644
index 0000000..0d17ae9
--- /dev/null
+++ b/test_conflict_evidence.py
@@ -0,0 +1,82 @@
+"""Offline conflict retention across public report formats."""
+import contextlib
+import csv
+import io
+import json
+import unittest
+from unittest.mock import patch
+
+import sharp_rsvg_rce_check as check
+
+
+class ConflictEvidenceTests(unittest.TestCase):
+ def report(self, sharp, native, fmt):
+ args = ['--library-source', 'global' if native else 'bundled',
+ '--sharp-build-source', 'upstream', '--librsvg-build-source', 'upstream',
+ '--format', fmt]
+ for value in sharp:
+ args += ['--sharp-version', value]
+ for value in native:
+ args += ['--librsvg-version', value]
+ out = io.StringIO()
+ with patch('socket.socket', side_effect=AssertionError('offline')), contextlib.redirect_stdout(out):
+ self.assertEqual(0, check.main(args))
+ return out.getvalue()
+
+ def test_both_components_retain_distinct_conflicts_in_all_formats(self):
+ for fmt in ('json', 'csv', 'html'):
+ with self.subTest(format=fmt):
+ text = self.report(['0.35.4', '0.35.5'], ['2.63.1', '2.63.2'], fmt)
+ for observation in ('Sharp version observation:', 'librsvg version observation:',
+ '0.35.4, 0.35.5', '2.63.1, 2.63.2'):
+ self.assertIn(observation, text)
+ if fmt == 'json':
+ result = json.loads(text)['results'][0]
+ elif fmt == 'csv':
+ result = next(csv.DictReader(io.StringIO(text)))
+ else:
+ self.assertIn('unknown', text)
+ self.assertIn('not_tested', text)
+ continue
+ self.assertEqual('unknown', result['status'])
+ self.assertEqual('not_tested', result['exploitability'])
+ if fmt == 'json':
+ self.assertIsNone(result['component']['version'])
+
+ def test_different_conflicting_pairs_are_distinguishable(self):
+ for fmt in ('json', 'csv', 'html'):
+ with self.subTest(format=fmt):
+ self.assertNotEqual(self.report(['0.35.4', '0.35.5'], [], fmt),
+ self.report(['0.35.3', '0.35.6'], [], fmt))
+ self.assertNotEqual(self.report([], ['2.63.1', '2.63.2'], fmt),
+ self.report([], ['2.63.0', '2.63.3'], fmt))
+
+ def test_qualified_or_secret_bearing_values_are_not_echoed(self):
+ unsafe = ['0.35.5+private-secret', '', '=private-secret']
+ for fmt in ('json', 'csv', 'html'):
+ with self.subTest(format=fmt):
+ text = self.report(['0.35.4'] + unsafe, ['2.63.2'] + unsafe, fmt)
+ self.assertIn('0.35.4', text)
+ self.assertIn('2.63.2', text)
+ self.assertNotIn('private-secret', text)
+ self.assertIn('unknown', text)
+ self.assertIn('not_tested', text)
+
+ def test_duplicate_and_reordered_observations_have_stable_evidence(self):
+ for fmt in ('json', 'csv', 'html'):
+ with self.subTest(format=fmt):
+ self.assertEqual(self.report(['0.35.5', '0.35.4', '0.35.4'], [], fmt),
+ self.report(['0.35.4', '0.35.5'], [], fmt))
+
+ def test_maximum_observations_preserve_bounded_validated_evidence(self):
+ versions = ['0.35.' + str(i) for i in range(8)]
+ result = check.assess_record({'asset_id': 'bounded', 'sharp_versions': versions})
+ check.validate_result(result)
+ detail = next(item['detail'] for item in result['evidence'] if item['id'] == 'sharp-versions')
+ for version in versions:
+ self.assertIn(version, detail)
+ self.assertLess(len(detail), 2048)
+
+
+if __name__ == '__main__':
+ unittest.main()