CVE-2026-11841

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

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

Score 9.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-28. A secondary CVSS source baseline 9.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
9.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 9.4Exploit: None knownExposed services: Not assessed

For InspectorP61x and InspectorP62x: Users are recommended to upgrade to version 5.4.0 (from the CVE record's solution, SICK AG) — apply it.

An attacker may perform unauthenticated read and write operations on sensitive filesystem areas via the AppEngine Fileaccess over HTTP due to improper access restrictions. A critical filesystem directory was unintentionally exposed through the HTTP-based file access feature, allowing access without authentication. This includes device parameter files, enabling an attacker to read and modify application settings, including customer-defined passwords. Additionally, exposure of the custom application directory may allow execution of arbitrary Lua code within the sandboxed AppEngine environment.

CVSS v3
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
58
EG Risk 58/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)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 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 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: For InspectorP61x and InspectorP62x: Users are recommended to upgrade to version 5.4.0 (from the CVE record's solution, SICK AG). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
57th
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 (9.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-18). 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: 3 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).

For InspectorP61x and InspectorP62x: Users are recommended to upgrade to version 5.4.0 (from the CVE record's solution, SICK AG). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 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 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

July 28, 2026

Last Modified

September 9, 2026

Vendor Advisories for CVE-2026-11841(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 19× in last 7d / 74× 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 425 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 325 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-11841?
CVE-2026-11841 is a critical-severity vulnerability; its CVE record was published on July 28, 2026. An attacker may perform unauthenticated read and write operations on sensitive filesystem areas via the AppEngine Fileaccess over HTTP due to improper access restrictions. A critical filesystem directory was unintentionally exposed through the HTTP-based file access feature, allowing access without…
When was CVE-2026-11841 made public?
CVE-2026-11841 was made public on July 28, 2026: that is the date its CVE record's CNA, SICK AG, gives for when the vulnerability was made public. The CVE record itself was published on July 28, 2026. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-11841 actively exploited?
CVE-2026-11841 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-11841?
CVE-2026-11841 has a CVSS base score of 9.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-11841?
The CVE record's solution for CVE-2026-11841, written by its CNA SICK AG, names the fix: "For InspectorP61x and InspectorP62x: Users are recommended to upgrade to version 5.4.0." The vendor advisories EchelonGraph has for CVE-2026-11841 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-11841?

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