CVE-2026-13592 — liftoff-sr CIPster EtherNet IP Message append out-of-bounds write
A vulnerability was detected in liftoff-sr CIPster up to e8e9dba09bf56962807d3504b783ccdb6287f3e4. Affected by this issue is the function BufWriter::append of the component EtherNet IP Message Handler. Performing a manipulation results in out-of-bounds write. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The patch is named 3a0159ed43125dcd024a1965f0289cb186bae9ff. To fix this issue, it is recommended to deploy a patch.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.6% (30-day exploitation probability)+7
- Technical severity (high)+6
- CISA SSVC: exploitation "poc"+5
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Liftoff-sr CIPster).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Liftoff-sr | CIPster | version e8e9dba09bf56962807d3504b783ccdb6287f3e4 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.9 | CVSS 4.0 | Medium | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 5.5 | CVSS 4.0 | Medium | — | — | cna@vuldb.com via NIST National Vulnerability Database |
| 7.3 | CVSS 3.1 | High | 3.9 | 3.4 | cna@vuldb.com via NIST National Vulnerability Database |
| 7.3 | CVSS 3.1 | High | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 7.3 | CVSS 3.0 | High | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 7.5 | CVSS 2.0 | High | 10.0 | 6.4 | cna@vuldb.com via NIST National Vulnerability Database |
| 7.5 | CVSS 2.0 | High | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L (score shown at the top: cna@vuldb.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CWE-119 · Buffer Errors (Improper Restriction of Operations within Memory Bounds)
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.64%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · liftoff-sr/cipster
- SSVC assessment updated
- Record published
- CVSS changed · 7.3
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
9 on the record
- github.com/liftoff-sr/CIPster/commit/3a0159ed43125dcd024a1965f0289cb186bae9ff
- vuldb.com/vuln/374596/cti
- github.com/liftoff-sr/CIPster/issues/48
- vuldb.com/cve/CVE-2026-13592
- github.com/liftoff-sr/CIPster/
- github.com/user-attachments/files/28452971/poc.zip
- vuldb.com/vuln/374596
- vuldb.com/submit/844566
- github.com/liftoff-sr/CIPster/issues/48
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-76987 liftoff-sr CIPster Generic Attribute Logic ciptypes.h SetAttrData memory corruption Aug 20, 2026
- Medium CVE-2026-76988 liftoff-sr CIPster ForwardOpen cipconnectionmanager.cc forward_open out-of-bounds Aug 20, 2026
- Medium CVE-2026-76989 liftoff-sr CIPster TCP Encapsulation Receive Path encap.cc out-of-bounds Aug 20, 2026
- Medium CVE-2026-16013 liftoff-sr CIPster cipepath.cc deserialize_symbolic out-of-bounds Jul 17, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-13592 is "liftoff-sr CIPster EtherNet IP Message append out-of-bounds write", rated High. It affects CIPster (Liftoff-sr); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.3 describes technical severity. EPSS 0.64% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.