{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114116 exists.","fix":"No fix has been published for CVE-2026-114116 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-114116 is a medium-severity vulnerability in vyperlang vyper, published on 21 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-114116 and fix it if it is affected.\n\nWhat it is: CVE-2026-114116 is a medium-severity vulnerability in vyperlang vyper, published on 21 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114116 exists.\n\nAffected product: vyperlang vyper. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-114116/ (Markdown: https://insights.sbomify.com/CVE-2026-114116/index.md)","id":"CVE-2026-114116","markdown":"https://insights.sbomify.com/CVE-2026-114116/index.md","name":"CVE-2026-114116","record":{"aliases":["GHSA-2gvm-cwr3-3pcg","GHSA-wvx7-39qj-2g9v"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-436","name":"Interpretation Conflict"}],"description":"Vyper 0.1.0b1 before 0.1.0b17 and 0.4.1 through 0.5.0b1 builds its source-line table with str.splitlines(), which treats characters like form feed and U+2028 as line breaks the Python parser ignores, so numeric literals are classified and validated from shifted source text. An attacker contributing source code can hide these characters in comments, strings or indentation to silently change address, integer or decimal constants.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Vyper through 0.5.0b1 Literal Value Manipulation via Line Separators","id":"CVE-2026-114116","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Vyper 0.3.8 through 0.5.0b1 Optimizer Miscompilation of msg.value | K in Ternary Branches","id":"CVE-2026-114117"},"packages":[],"prev":{"headline":"Vyper 0.3.8 through 0.5.0b1 Memory Misread via Ternary Nested Array Selection","id":"CVE-2026-114115"},"products":["vyper"],"published":"2026-10-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-28","vendors":["vyperlang"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-114116/"}