A vulnerability has been identified in RUGGEDCOM i800, RUGGEDCOM i800NC, RUGGEDCOM i801, RUGGEDCOM i801NC, RUGGEDCOM i802, RUGGEDCOM i802NC, RUGGEDCOM i803, RUGGEDCOM i803NC, RUGGEDCOM M2100, RUGGEDCOM M2100F, RUGGEDCOM M2100NC, RUGGEDCOM M2200, RUGGEDCOM M2200F, RUGGEDCOM M2200NC, RUGGEDCOM M969, RUGGEDCOM M969F, RUGGEDCOM M969NC, RUGGEDCOM RMC30, RUGGEDCOM RMC30NC, RUGGEDCOM RMC8388 V4.X, RUGGEDCOM RMC8388 V5.X, RUGGEDCOM RMC8388NC V4.X, RUGGEDCOM RMC8388NC V5.X, RUGGEDCOM RP110, RUGGEDCOM RP110NC, RUGGEDCOM RS1600, RUGGEDCOM RS1600F, RUGGEDCOM RS1600FNC, RUGGEDCOM RS1600NC, RUGGEDCOM RS1600T, RUGGEDCOM RS1600TNC, RUGGEDCOM RS400, RUGGEDCOM RS400F, RUGGEDCOM RS400NC, RUGGEDCOM RS401, RUGGEDCOM RS401NC, RUGGEDCOM RS416, RUGGEDCOM RS416F, RUGGEDCOM RS416NC, RUGGEDCOM RS416NCv2 V4.X, RUGGEDCOM RS416NCv2 V5.X, RUGGEDCOM RS416P, RUGGEDCOM RS416PF, RUGGEDCOM RS416PNC, RUGGEDCOM RS416PNCv2 V4.X, RUGGEDCOM RS416PNCv2 V5.X, RUGGEDCOM RS416Pv2 V4.X, RUGGEDCOM RS416Pv2 V5.X, RUGGEDCOM RS416v2 V4.X, RUGGEDCOM RS416v2 V5.X, RUGGEDCOM RS8000, RUGGEDCOM RS8000A, RUGGEDCOM RS8000ANC, RUGGEDCOM RS8000H, RUGGEDCOM RS8000HNC, RUGGEDCOM RS8000NC, RUGGEDCOM RS8000T, RUGGEDCOM RS8000TNC, RUGGEDCOM RS900, RUGGEDCOM RS900 (32M) V4.X, RUGGEDCOM RS900 (32M) V5.X, RUGGEDCOM RS900F, RUGGEDCOM RS900G, RUGGEDCOM RS900G (32M) V4.X, RUGGEDCOM RS900G (32M) V5.X, RUGGEDCOM RS900GF, RUGGEDCOM RS900GNC, RUGGEDCOM RS900GNC(32M) V4.X, RUGGEDCOM RS900GNC(32M) V5.X, RUGGEDCOM RS900GP, RUGGEDCOM RS900GPF, RUGGEDCOM RS900GPNC, RUGGEDCOM RS900L, RUGGEDCOM RS900LNC, RUGGEDCOM RS900M-GETS-C01, RUGGEDCOM RS900M-GETS-XX, RUGGEDCOM RS900M-STND-C01, RUGGEDCOM RS900M-STND-XX, RUGGEDCOM RS900MNC-GETS-C01, RUGGEDCOM RS900MNC-GETS-XX, RUGGEDCOM RS900MNC-STND-XX, RUGGEDCOM RS900MNC-STND-XX-C01, RUGGEDCOM RS900NC, RUGGEDCOM RS900NC(32M) V4.X, RUGGEDCOM RS900NC(32M) V5.X, RUGGEDCOM RS900W, RUGGEDCOM RS910, RUGGEDCOM RS910L, RUGGEDCOM RS910LNC, RUGGEDCOM RS910NC, RUGGEDCOM RS910W, RUGGEDCOM RS920L, RUGGEDCOM RS920LNC, RUGGEDCOM RS920W, RUGGEDCOM RS930L, RUGGEDCOM RS930LNC, RUGGEDCOM RS930W, RUGGEDCOM RS940G, RUGGEDCOM RS940GF, RUGGEDCOM RS940GNC, RUGGEDCOM RS969, RUGGEDCOM RS969NC, RUGGEDCOM RSG2100, RUGGEDCOM RSG2100 (32M) V4.X, RUGGEDCOM RSG2100 (32M) V5.X, RUGGEDCOM RSG2100F, RUGGEDCOM RSG2100NC, RUGGEDCOM RSG2100NC(32M) V4.X, RUGGEDCOM RSG2100NC(32M) V5.X, RUGGEDCOM RSG2100P, RUGGEDCOM RSG2100P (32M) V4.X, RUGGEDCOM RSG2100P (32M) V5.X, RUGGEDCOM RSG2100PF, RUGGEDCOM RSG2100PNC, RUGGEDCOM RSG2100PNC (32M) V4.X, RUGGEDCOM RSG2100PNC (32M) V5.X, RUGGEDCOM RSG2200, RUGGEDCOM RSG2200F, RUGGEDCOM RSG2200NC, RUGGEDCOM RSG2288 V4.X, RUGGEDCOM RSG2288 V5.X, RUGGEDCOM RSG2288NC V4.X, RUGGEDCOM RSG2288NC V5.X, RUGGEDCOM RSG2300 V4.X, RUGGEDCOM RSG2300 V5.X, RUGGEDCOM RSG2300F, RUGGEDCOM RSG2300NC V4.X, RUGGEDCOM RSG2300NC V5.X, RUGGEDCOM RSG2300P V4.X, RUGGEDCOM RSG2300P V5.X, RUGGEDCOM RSG2300PF, RUGGEDCOM RSG2300PNC V4.X, RUGGEDCOM RSG2300PNC V5.X, RUGGEDCOM RSG2488 V4.X, RUGGEDCOM RSG2488 V5.X, RUGGEDCOM RSG2488F, RUGGEDCOM RSG2488NC V4.X, RUGGEDCOM RSG2488NC V5.X, RUGGEDCOM RSG907R, RUGGEDCOM RSG908C, RUGGEDCOM RSG909R, RUGGEDCOM RSG910C, RUGGEDCOM RSG920P V4.X, RUGGEDCOM RSG920P V5.X, RUGGEDCOM RSG920PNC V4.X, RUGGEDCOM RSG920PNC V5.X, RUGGEDCOM RSL910, RUGGEDCOM RSL910NC, RUGGEDCOM RST2228, RUGGEDCOM RST2228P, RUGGEDCOM RST916C, RUGGEDCOM RST916P. Affected devices improperly handle partial HTTP requests which makes them vulnerable to slowloris attacks. This could allow a remote attacker to create a denial of service condition that persists until the attack ends.
CVE-2022-39158
“▲” beside the score: it is higher than NVD's CVSS score.
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-09-14. NVD baseline CVSS 5.3; sources differ by 2.2.
- Lower severity and no public exploit yet
A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).
- CVSS v3
- 5.3
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 49EG Risk 49/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation1.5% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation. - EPSS PROB
- 1.5%
- EPSS %ILE
- 73rd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 1.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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
September 13, 2022
Last Modified
August 12, 2025
References (4)
- productcert@siemenshttps://cert-portal.siemens.com/productcert/html/ssa-459643.html
- productcert@siemenshttps://cert-portal.siemens.com/productcert/html/ssa-787941.html
- productcert@siemens · CVE Programhttps://cert-portal.siemens.com/productcert/pdf/ssa-459643.pdfPatch · Vendor Advisory
- productcert@siemens · CVE Programhttps://cert-portal.siemens.com/productcert/pdf/ssa-787941.pdf
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 32× 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 91 of 185 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. 9 repeat rows among the latest 100 are merged into the row they repeat. The 94 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-22 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-21 06:24 UTCEG score recompute
- 2026-10-21 06:24 UTCGHSA enrichmentGHSA-grpv-g4qc-62cg · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-20 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-19 16:28 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-18 16:28 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-18 08:28 UTCEG score recompute
- 2026-10-17 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-16 16:35 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-15 16:28 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-13 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-12 18:48 UTCEG score recompute
- 2026-10-12 16:30 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-10-11 23:12 UTCEG score recompute
- 2026-10-11 13:44 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-10-09 20:04 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-10-08 16:40 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-10-06 15:14 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-10-05 17:40 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-10-02 16:23 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
Show 66 moreShow fewer
- 2026-10-01 19:47 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-30 16:03 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-29 15:16 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-24 14:00 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-22 14:45 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-19 15:38 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-17 19:24 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-16 14:05 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-15 03:07 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-12 14:57 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-11 14:50 UTCEPSS rescoreEPSS 1.5% · 71st percentile
- 2026-09-11 09:33 UTCEPSS rescoreEPSS 1.5% · 71st percentile
- 2026-09-08 21:57 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-07 15:58 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-04 13:57 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-30 19:14 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-30 01:19 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-28 21:38 UTCEPSS rescoreEPSS 1.3% · 66th percentile
- 2026-08-27 14:22 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-26 14:43 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-24 14:13 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-23 00:17 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-21 23:46 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-08-20 22:52 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-08-19 17:01 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-08-18 13:45 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-08-17 13:44 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-08-16 14:53 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-08-16 02:11 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-08-15 01:27 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-08-13 21:58 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-08-12 13:48 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-08-11 13:39 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-08-10 14:08 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-09 13:44 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-08 16:34 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-07 16:24 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-06 13:44 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-04 15:07 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-04 10:35 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-02 02:24 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-01 04:13 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-07-30 16:25 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-07-30 01:28 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-07-28 15:33 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-07-26 14:52 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-07-25 14:15 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-07-24 14:15 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-07-23 14:16 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-07-23 02:13 UTCEG score recompute
- 2026-07-22 23:00 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-07-21 15:22 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-07-20 17:05 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-07-19 14:29 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-07-19 02:27 UTCEPSS rescoreEPSS 1.2% · 65th percentile
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2022-39158?
When was the CVE record for CVE-2022-39158 published?
Is CVE-2022-39158 actively exploited?
What is the CVSS score of CVE-2022-39158?
How do I remediate CVE-2022-39158?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2022-39158
Is Your Infrastructure Affected by CVE-2022-39158?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.