{"answers":{"affected":"3 open source packages ship an affected version, including surfio.","exploited":"There is no known exploitation of CVE-2026-55211 in the wild and no public exploit code.","fix":"Upgrade surfio to 0.0.19 or later.","what":"CVE-2026-55211 is a critical memory corruption vulnerability in equinor surfio, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-55211 and fix it if it is affected.\n\nWhat it is: CVE-2026-55211 is a critical memory corruption vulnerability in equinor surfio, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-55211 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- surfio (PyPI): affected all versions; fixed in 0.0.19\n- surfio (PyPI): affected all versions; fixed in 0.0.19\n- surfio (PyPI): affected all versions; fixed in 0.0.19\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-55211/ (Markdown: https://insights.sbomify.com/CVE-2026-55211/index.md)","id":"CVE-2026-55211","markdown":"https://insights.sbomify.com/CVE-2026-55211/index.md","name":"CVE-2026-55211","record":{"aliases":["GHSA-rcr2-hggw-43wm","PYSEC-2026-3701"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Python surface file library","requires_auth":"none","summary":"Attackers can trigger out-of-bounds reads and potential code execution by providing malicious IRAP files to applications using the surfio library.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Surfio is a library for reading and writing surface files. Prior to 0.0.19, surfio does not correctly validate size fields in IRAP files, leading to a buffer overflow when untrusted files are parsed. The severity assumes surfio is used to parse untrusted files in a networking context such as a web service. This issue is fixed in version 0.0.19.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"surfio IRAP header size fields cause out-of-bounds reads","id":"CVE-2026-55211","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":3,"n_references":5,"next":{"headline":"Pimcore: Insufficient Permission Check on Class Definition Creation Endpoint Allows Privilege Escalation","id":"CVE-2026-55212"},"packages":[{"ecosystem":"PyPI","fixed":["0.0.19"],"introduced":["0"],"last_affected":[],"package":"surfio","purl":null,"source":"GHSA-rcr2-hggw-43wm"},{"ecosystem":"PyPI","fixed":["0.0.19"],"introduced":["0"],"last_affected":[],"package":"surfio","purl":"pkg:pypi/surfio","source":"GHSA-rcr2-hggw-43wm"},{"ecosystem":"PyPI","fixed":["0.0.19"],"introduced":["0"],"last_affected":[],"package":"surfio","purl":"pkg:pypi/surfio","source":"PYSEC-2026-3701"}],"prev":{"headline":"Joplin: SAML SSO account takeover via email-based account linking (missing is_external check in ssoLogin)","id":"CVE-2026-55210"},"products":["surfio"],"published":"2026-09-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["equinor"]},"summary":"Attackers can trigger out-of-bounds reads and potential code execution by providing malicious IRAP files to applications using the surfio library.","url":"https://insights.sbomify.com/CVE-2026-55211/"}