{"answers":{"affected":"2 open source packages ship an affected version, including icalendar. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33635 exists.","fix":"Upgrade icalendar to 2.12.2 or later.","what":"CVE-2026-33635 is a medium-severity vulnerability in icalendar, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-33635 and fix it if it is affected.\n\nWhat it is: CVE-2026-33635 is a medium-severity vulnerability in icalendar, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33635 exists.\n\nAffected packages and fixed versions:\n- icalendar (RubyGems): affected from 2.0.0; fixed in 2.12.2\n- icalendar (RubyGems): affected from 2.0.0; fixed in 2.12.2\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-33635/ (Markdown: https://insights.sbomify.com/CVE-2026-33635/index.md)","id":"CVE-2026-33635","markdown":"https://insights.sbomify.com/CVE-2026-33635/index.md","name":"CVE-2026-33635","record":{"aliases":["DEBIAN-CVE-2026-33635","GHSA-pv9c-9mfh-hvxq","UBUNTU-CVE-2026-33635"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby iCalendar library","requires_auth":"none","summary":"Attackers can inject arbitrary calendar lines into generated ICS files via unsanitized URI properties, potentially manipulating calendar data in downstream clients.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"icalendar","vendor":"icalendar_project"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-93","name":"Improper Neutralization of CRLF Sequences"}],"description":"iCalendar is a Ruby library for dealing with iCalendar files in the iCalendar format defined by RFC-5545. Starting in version 2.0.0 and prior to version 2.12.2, .ics serialization does not properly sanitize URI property values, enabling ICS injection through attacker-controlled input, adding arbitrary calendar lines to the output. `Icalendar::Values::Uri` falls back to the raw input string when `URI.parse` fails and later serializes it with `value.to_s` without removing or escaping `\\r` or `\\n` characters. That value is embedded directly into the final ICS line by the normal serializer, so a payload containing CRLF can terminate the original property and create a new ICS property or component. (It looks like you can inject via url, source, image, organizer, attach, attendee, conference, tzurl because of this). Applications that generate `.ics` files from partially untrusted metadata are impacted. As a result, downstream calendar clients or importers may process attacker-supplied content as if it were legitimate event data, such as added attendees, modified URLs, alarms, or other calendar fields. Version 2.12.2 contains a patch for the issue.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"iCalendar has ICS injection via unsanitized URI property values","id":"CVE-2026-33635","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"LIBPNG has ARM NEON Palette Expansion Out-of-Bounds Read on AArch64","id":"CVE-2026-33636"},"packages":[{"ecosystem":"RubyGems","fixed":["2.12.2"],"introduced":["2.0.0"],"last_affected":[],"package":"icalendar","purl":null,"source":"GHSA-pv9c-9mfh-hvxq"},{"ecosystem":"RubyGems","fixed":["2.12.2"],"introduced":["2.0.0"],"last_affected":[],"package":"icalendar","purl":"pkg:gem/icalendar","source":"GHSA-pv9c-9mfh-hvxq"}],"prev":{"headline":"Aquasecurity Trivy Embedded Malicious Code","id":"CVE-2026-33634"},"products":["icalendar"],"published":"2026-03-26","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":"US public information, NVD API terms","name":"NVD"},{"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-03-30","vendors":["icalendar"]},"summary":"Attackers can inject arbitrary calendar lines into generated ICS files via unsanitized URI properties, potentially manipulating calendar data in downstream clients.","url":"https://insights.sbomify.com/CVE-2026-33635/"}