CVE-2026-10800

LOWPre-NVD 3.63.6—
EchelonGraph scoreMEDIUM confidence

Score 3.6 from GitHub Security Advisory (severity: LOW) published 2026-06-04. a secondary CVSS source baseline 3.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
3.6
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A weakness has been identified in PaddlePaddle FastDeploy up to 2.4.1. Affected by this issue is the function hash_features of the file fastdeploy/multimodal/hasher.py of the component MultimodalHasher. Executing a manipulation can lead to use of weak hash. The attack requires local access. A high complexity level is associated with this attack. The exploitation is known to be difficult. This patch is called 374945747652a8d32965591c0c01a00c88b7067f. Applying a patch is advised to resolve this issue.

CVSS v3
3.6
EG Score
3.6(medium)
EG Risk
16(Track)
EG Risk 16/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity36% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.1%
KEV
Not listed

Published

June 4, 2026

Last Modified

July 22, 2026

References (8)

Vendor Advisories for CVE-2026-10800(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 03:04 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-19 14:30 UTCEPSS rescore
  5. 2026-07-18 10:04 UTCEPSS rescore
  6. 2026-07-16 17:02 UTCEPSS rescore
  7. 2026-07-16 00:21 UTCGHSA enrichment
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-13 22:30 UTCEPSS rescore
  10. 2026-07-13 06:12 UTCEPSS rescore
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-11 23:14 UTCGHSA enrichment
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-08 16:15 UTCGHSA enrichment
  15. 2026-07-08 15:15 UTCEPSS rescore
  16. 2026-07-08 15:15 UTCEPSS rescore
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-03 19:26 UTCGHSA enrichment
  20. 2026-06-29 21:52 UTCGHSA enrichment
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-26 15:00 UTCGHSA enrichment
  25. 2026-06-23 21:32 UTCEPSS rescore
Show 26 more
  1. 2026-06-23 02:31 UTCGHSA enrichment
  2. 2026-06-21 01:59 UTCEPSS rescore
  3. 2026-06-21 01:59 UTCEPSS rescore
  4. 2026-06-18 17:52 UTCEPSS rescore
  5. 2026-06-17 17:53 UTCEPSS rescore
  6. 2026-06-17 13:28 UTCGHSA enrichment
  7. 2026-06-15 17:48 UTCEPSS rescore
  8. 2026-06-14 23:18 UTCEPSS rescore
  9. 2026-06-14 06:35 UTCGHSA enrichment
  10. 2026-06-12 23:12 UTCEPSS rescore
  11. 2026-06-11 14:00 UTCEPSS rescore
  12. 2026-06-10 23:43 UTCGHSA enrichment
  13. 2026-06-10 22:18 UTCEPSS rescore
  14. 2026-06-10 13:22 UTCEPSS rescore
  15. 2026-06-08 14:17 UTCEPSS rescore
  16. 2026-06-08 14:17 UTCEPSS rescore
  17. 2026-06-07 16:52 UTCGHSA enrichment
  18. 2026-06-07 15:25 UTCEPSS rescore
  19. 2026-06-07 15:24 UTCEPSS rescore
  20. 2026-06-06 13:47 UTCEPSS rescore
  21. 2026-06-06 13:47 UTCEPSS rescore
  22. 2026-06-06 13:47 UTCEPSS rescore
  23. 2026-06-05 22:47 UTCEPSS rescore
  24. 2026-06-05 06:10 UTCEPSS rescore
  25. 2026-06-05 06:10 UTCEPSS rescore
  26. 2026-06-04 10:00 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10800?
CVE-2026-10800 is a low vulnerability published on June 4, 2026. A weakness has been identified in PaddlePaddle FastDeploy up to 2.4.1. Affected by this issue is the function hash_features of the file fastdeploy/multimodal/hasher.py of the component MultimodalHasher. Executing a manipulation can lead to use of weak hash. The attack requires local access. A high…
When was CVE-2026-10800 disclosed?
CVE-2026-10800 was first published in the National Vulnerability Database on June 4, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10800 actively exploited?
CVE-2026-10800 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10800?
CVE-2026-10800 has a CVSS v3 base score of 3.6 (NVD).
How do I remediate CVE-2026-10800?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10800, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10800

Explore →

Is Your Infrastructure Affected by CVE-2026-10800?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs