CVE-2026-16013

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

Score 5.3 from GitHub Security Advisory published 2026-07-17. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated
5.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

A vulnerability has been found in liftoff-sr CIPster up to 632336d414ef708a542377c1aa8d6fdb7c70a760. Affected by this issue is the function CipAppPath::deserialize_symbolic of the file source/src/cip/cipepath.cc. Such manipulation leads to out-of-bounds read. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. The name of the patch is 886a4d090e1c5b0475f0b1c2fe0606a8f0d6a519. A patch should be applied to remediate this issue.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/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)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (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: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

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

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

Exploitation public PoC (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

July 17, 2026

Last Modified

July 17, 2026

Advisory Details (3)

Auto-updated Jul 17, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
Web page

GitHub - liftoff-sr/CIPster: Ethernet/IP (Common Industrial Protocol) stack in C++. This started as a C to C++ conversion of C based OpENer. · GitHub

https://github.com/liftoff-sr/CIPster/
GitHub commit

commit 886a4d090e1c (liftoff-sr/CIPster)

Fix landed in liftoff-sr/CIPster commit 886a4d090e1c — awaiting tagged release

https://github.com/liftoff-sr/CIPster/commit/886a4d090e1c5b0475f0b1c2fe0606a8f0d6a519
Web page

Out-of-Bounds Read in `CipAppPath::deserialize_symbolic()` Reachable via `SendRRData` Unconnected Explicit Messaging · Issue #53 · liftoff-sr/CIPster · GitHub

https://github.com/liftoff-sr/CIPster/issues/53

Vendor Advisories for CVE-2026-16013(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 11× in last 7d / 33× 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 163 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 63 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16013?
CVE-2026-16013 is a medium-severity vulnerability; its CVE record was published on July 17, 2026. A vulnerability has been found in liftoff-sr CIPster up to 632336d414ef708a542377c1aa8d6fdb7c70a760. Affected by this issue is the function CipAppPath::deserialize_symbolic of the file source/src/cip/cipepath.cc. Such manipulation leads to out-of-bounds read. The attack may be launched remotely.…
When was the CVE record for CVE-2026-16013 published?
The CVE record for CVE-2026-16013 was published on July 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 July 17, 2026; the record at its source may have been updated since.
Is CVE-2026-16013 actively exploited?
CVE-2026-16013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16013?
CVE-2026-16013 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-16013?
An upstream fix for CVE-2026-16013 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-16013 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-16013?

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

Book a Demo →Browse All CVEs