# CVE-2026-16013: liftoff-sr CIPster cipepath.cc deserialize_symbolic out-of-bounds

> An out-of-bounds read in CIPster allows remote attackers to read memory or cause denial of service via crafted symbolic paths.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-w4qj-vxw3-g77r

## What is CVE-2026-16013?

CVE-2026-16013 is a medium-severity memory corruption vulnerability in liftoff-sr CIPster, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-16013?


## How do I fix CVE-2026-16013?

No fix has been published for CVE-2026-16013 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16013 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16013 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16013 and fix it if it is affected.

What it is: CVE-2026-16013 is a medium-severity memory corruption vulnerability in liftoff-sr CIPster, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16013 exists.

Affected product: liftoff-sr CIPster. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16013/ (Markdown: https://insights.sbomify.com/CVE-2026-16013/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16013
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16013
- OSV: https://osv.dev/vulnerability/CVE-2026-16013

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16013/
Summaries are generated and may contain mistakes; the official description above is the record.