What is CVE-2026-55211?

CVE-2026-55211 is a critical-severity out-of-bounds read vulnerability in surfio (pip), affecting versions < 0.0.19. It is fixed in 0.0.19. A read operation accesses a memory location beyond the intended buffer boundary.

How severe is CVE-2026-55211?

CVE-2026-55211 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of surfio are affected by CVE-2026-55211?

surfio (pip) versions < 0.0.19 is affected.

Is there a fix for CVE-2026-55211?

Yes. CVE-2026-55211 is fixed in 0.0.19. Upgrade to this version or later.

Is CVE-2026-55211 exploitable, and should I be worried?

Whether CVE-2026-55211 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-55211 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-55211?

Upgrade surfio to 0.0.19 or later.

CVE-2026-55211 in surfio

Q: How severe is CVE-2026-55211?

CVE-2026-55211 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of surfio are affected by CVE-2026-55211?

surfio (pip) versions < 0.0.19 is affected.

Q: Is there a fix for CVE-2026-55211?

Yes. CVE-2026-55211 is fixed in 0.0.19. Upgrade to this version or later.

Q: Is CVE-2026-55211 exploitable, and should I be worried?

Whether CVE-2026-55211 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-55211 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-55211?

Upgrade surfio to 0.0.19 or later.

Summary

surfio has an out-of-bounds read

Impact

Prior to version 0.0.19, surfio would not correctly validate size fields in irap files, leading to a buffer overflow . The severity rating assumes that surfio is used to parse untrused files in a networking context such as a web service.

A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.

CVE-2026-55211 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.19); upgrading removes the vulnerable code path.

Affected versions

surfio (< 0.0.19)

Security releases

surfio → 0.0.19 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The bug has been patched in version 0.0.19

Frequently Asked Questions

What is CVE-2026-55211? CVE-2026-55211 is a critical-severity out-of-bounds read vulnerability in surfio (pip), affecting versions < 0.0.19. It is fixed in 0.0.19. A read operation accesses a memory location beyond the intended buffer boundary.
How severe is CVE-2026-55211? CVE-2026-55211 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of surfio are affected by CVE-2026-55211? surfio (pip) versions < 0.0.19 is affected.
Is there a fix for CVE-2026-55211? Yes. CVE-2026-55211 is fixed in 0.0.19. Upgrade to this version or later.
Is CVE-2026-55211 exploitable, and should I be worried? Whether CVE-2026-55211 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-55211 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-55211? Upgrade surfio to 0.0.19 or later.