{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-47088 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-47088 is a low-severity vulnerability in cyrusimap Cyrus IMAP, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-47088 and fix it if it is affected.\n\nWhat it is: CVE-2026-47088 is a low-severity vulnerability in cyrusimap Cyrus IMAP, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-47088 in the wild and no public exploit code.\n\nAffected product: cyrusimap Cyrus IMAP. 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-47088/ (Markdown: https://insights.sbomify.com/CVE-2026-47088/index.md)","id":"CVE-2026-47088","markdown":"https://insights.sbomify.com/CVE-2026-47088/index.md","name":"CVE-2026-47088","record":{"aliases":["DEBIAN-CVE-2026-47088","GHSA-f77j-qm5m-p6cw","UBUNTU-CVE-2026-47088"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Cyrus IMAP server","requires_auth":"low_privilege","summary":"An authenticated user can read heap memory by crafting a specific email message, potentially exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-126","name":"Buffer Over-read"}],"description":"An issue was discovered in cyrus-imapd in Cyrus IMAP through 3.12.2. There is heap exposure in nested MIME comment parsing. An authenticated IMAP user could craft an email message containing an RFC 822 comment ending with a backslash. When parsing the message, the server would read past the message's end in memory, and read into the heap, returning the read content to the user.","ecosystems":[],"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":"Information disclosure in Cyrus IMAP","id":"CVE-2026-47088","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in Cyrus IMAP","id":"CVE-2026-47089"},"packages":[],"prev":{"headline":"Auth bypass in Cyrus IMAP","id":"CVE-2026-47087"},"products":["Cyrus IMAP"],"published":"2026-07-16","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-16","vendors":["cyrusimap"]},"summary":"An authenticated user can read heap memory by crafting a specific email message, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-47088/"}