CVE-2026-11857

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (18th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
8.4EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.4Exploit: None knownExposed services: Not assessed

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

Quanos SCHEMA ST4 on-premises contains a local privilege escalation vulnerability in the Client Update Service due to insecure deserialization in the .NET Remoting service. The service is configured with TypeFilterLevel.Full and is bound to local interfaces only through named pipes. A local authenticated attacker can connect to the local named pipe, obtain the .NET Remoting endpoint, and send specially crafted serialized objects. Successful exploitation results in arbitrary code execution in the context of the update process with NT AUTHORITY\SYSTEM privileges. Network-only exploitation is not possible and local host access with an authenticated user session is required.

CVSS v3
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
38
EG Risk 38/100

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 (value × EchelonGraph’s weight)
Severity84% × 45%
The EG Score, 8.4 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 17, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Jun 18, 2026
No fix on record yet.
Web page

Multiple Vulnerabilities in Quanos Content Solutions SCHEMA ST4 - SEC Consult

https://r.sec-consult.com/quanos

Vendor Advisories for CVE-2026-11857(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 243 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 143 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 20:13 UTCEG score recompute
  2. 2026-10-11 18:25 UTCEG score recompute
  3. 2026-10-11 14:58 UTCEG score recompute
  4. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  5. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  6. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  7. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  8. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  9. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  12. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  13. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  14. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  15. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  16. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  18. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  19. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  20. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  21. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  22. 2026-09-14 03:17 UTCEG score recompute
  23. 2026-09-14 03:17 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  24. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  25. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
Show 75 more
  1. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  3. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  4. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  5. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  7. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  8. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-08-30 22:31 UTCEG score recompute
  11. 2026-08-30 22:31 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  12. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-08-24 22:31 UTCEG score recompute
  17. 2026-08-24 22:31 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  18. 2026-08-23 20:56 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  19. 2026-08-23 08:58 UTCEG score recompute
  20. 2026-08-23 08:58 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  21. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  22. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-08-21 20:19 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  24. 2026-08-21 08:21 UTCEG score recompute
  25. 2026-08-21 08:21 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  26. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  27. 2026-08-20 20:23 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  28. 2026-08-20 08:24 UTCEG score recompute
  29. 2026-08-20 08:24 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  30. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  31. 2026-08-19 08:18 UTCEG score recompute
  32. 2026-08-19 08:18 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  33. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  34. 2026-08-17 09:54 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  35. 2026-08-16 21:57 UTCEG score recompute
  36. 2026-08-16 21:57 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  37. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  38. 2026-08-16 09:58 UTCEG score recompute
  39. 2026-08-16 09:58 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  40. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  41. 2026-08-15 22:01 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  42. 2026-08-15 09:47 UTCEG score recompute
  43. 2026-08-15 09:47 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  44. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  45. 2026-08-14 20:42 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  46. 2026-08-14 08:44 UTCEG score recompute
  47. 2026-08-14 08:44 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  48. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  49. 2026-08-13 20:46 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  50. 2026-08-13 08:42 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  51. 2026-08-12 20:45 UTCEG score recompute
  52. 2026-08-12 20:45 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  53. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  54. 2026-08-12 08:47 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  55. 2026-08-11 20:49 UTCEG score recompute
  56. 2026-08-11 20:49 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  57. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  58. 2026-08-11 08:51 UTCEG score recompute
  59. 2026-08-11 08:51 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  60. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  61. 2026-08-10 20:53 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  62. 2026-08-10 08:54 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  63. 2026-08-09 20:57 UTCEG score recompute
  64. 2026-08-09 20:57 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  65. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  66. 2026-08-09 08:59 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  67. 2026-08-08 21:01 UTCEG score recompute
  68. 2026-08-08 21:01 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  69. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  70. 2026-08-08 09:03 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  71. 2026-08-07 21:05 UTCEG score recompute
  72. 2026-08-07 21:05 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  73. 2026-08-07 09:07 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH
  74. 2026-08-06 21:09 UTCEG score recompute
  75. 2026-08-06 21:09 UTCGHSA enrichmentGHSA-fmx7-jmr3-4jw2 · GitHub severity HIGH

Frequently asked(5)

What is CVE-2026-11857?
CVE-2026-11857 is a high-severity vulnerability; its CVE record was published on June 17, 2026. Quanos SCHEMA ST4 on-premises contains a local privilege escalation vulnerability in the Client Update Service due to insecure deserialization in the .NET Remoting service. The service is configured with TypeFilterLevel.Full and is bound to local interfaces only through named pipes. A local…
When was the CVE record for CVE-2026-11857 published?
The CVE record for CVE-2026-11857 was published on June 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-11857 actively exploited?
CVE-2026-11857 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-11857?
CVE-2026-11857 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-11857?
No fix for CVE-2026-11857 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-11857 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-11857?

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