A vulnerability has been identified in SIMATIC Field PG M5 (All versions), SIMATIC Field PG M6 (All versions < V26.01.12), SIMATIC IPC BX-21A (All versions < V31.01.07), SIMATIC IPC BX-32A (All versions < V29.01.07), SIMATIC IPC BX-39A (All versions < V29.01.07), SIMATIC IPC BX-59A (All versions < V32.01.04), SIMATIC IPC PX-32A (All versions < V29.01.07), SIMATIC IPC PX-39A (All versions < V29.01.07), SIMATIC IPC PX-39A PRO (All versions < V29.01.07), SIMATIC IPC RC-543A (All versions < V36.01.03), SIMATIC IPC RC-543B (All versions < V35.01.12), SIMATIC IPC RW-543A (All versions < V1.1.4), SIMATIC IPC RW-543B (All versions < V35.02.10), SIMATIC IPC127E (All versions < V27.01.11), SIMATIC IPC227E (All versions), SIMATIC IPC227G (All versions < V28.01.14), SIMATIC IPC277E (All versions), SIMATIC IPC277G (All versions < V28.01.14), SIMATIC IPC277G PRO (All versions < V28.01.14), SIMATIC IPC3000 SMART V3 (All versions), SIMATIC IPC327G (All versions < V28.01.14), SIMATIC IPC347G (All versions), SIMATIC IPC377G (All versions < V28.01.14), SIMATIC IPC427E (All versions < V21.01.21), SIMATIC IPC477E (All versions < V21.01.21), SIMATIC IPC477E PRO (All versions < V21.01.21), SIMATIC IPC527G (All versions), SIMATIC IPC627E (All versions < V25.02.15), SIMATIC IPC647E (All versions < V25.02.15), SIMATIC IPC677E (All versions < V25.02.15), SIMATIC IPC847E (All versions < V25.02.15), SIMATIC ITP1000 (All versions). The affected devices have insufficient protection mechanism for the EFI(Extensible Firmware Interface) variables stored on the device. This could allow an authenticated attacker to disable the BIOS password without proper authorization by directly communicate with the flash controller.
CVE-2024-56182
“—” beside the score: it is equal to NVD's CVSS score.
Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2025-03-11. NVD baseline CVSS 8.2; sources differ by 0.0.
Also known asEUVD-2024-54269 (ENISA EUVD) · GHSA-x7x2-6gw9-jg8m (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
The CVE record's CNA (Siemens) lists Siemens SIMATIC Field PG M6 versions before V26.01.12; Siemens SIMATIC IPC BX-21A versions before V31.01.07; Siemens SIMATIC IPC BX-32A versions before V29.01.07 as affected, and 4 more products. No release containing a fix is confirmed on record.
- CVSS v3
- 8.2
- EG Score
- 8.2HIGHmedium confidence
- EG Risk
- 37EG Risk 37/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)Severity82% × 45%Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.2% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule. - EPSS PROB
- 0.2%
- EPSS %ILE
- 11th
- 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 (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
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. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.
No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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
March 11, 2025
Last Modified
September 8, 2026
Advisory Details (1)
Auto-updated May 12, 2026Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 38× 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 95 of 214 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 119 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 16:41 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-27 19:13 UTCEG score recompute
- 2026-10-27 19:13 UTCGHSA enrichmentGHSA-x7x2-6gw9-jg8m · GitHub severity HIGH · GitHub CVSS 8.2
- 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-25 16:55 UTCEG score recompute
- 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-19 15:29 UTCEG score recompute
- 2026-10-19 15:29 UTCGHSA enrichmentGHSA-x7x2-6gw9-jg8m · GitHub severity HIGH · GitHub CVSS 8.2
- 2026-10-18 05:59 UTCEG score recompute
- 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
Show 70 moreShow fewer
- 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-12 17:37 UTCEG score recompute
- 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-11 21:03 UTCEG score recompute
- 2026-10-11 15:55 UTCEG score recompute
- 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-02 16:24 UTCEG score recompute
- 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-08 09:49 UTCGHSA enrichmentGHSA-x7x2-6gw9-jg8m · GitHub severity HIGH · GitHub CVSS 8.2
- 2026-09-08 08:39 UTCEG score recompute
- 2026-09-08 08:39 UTCGHSA enrichmentGHSA-x7x2-6gw9-jg8m · GitHub severity HIGH · GitHub CVSS 8.2
- 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-11 13:41 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2024-56182?
When was the CVE record for CVE-2024-56182 published?
Is CVE-2024-56182 actively exploited?
What is the CVSS score of CVE-2024-56182?
How do I remediate CVE-2024-56182?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2024-56182
Is Your Infrastructure Affected by CVE-2024-56182?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.