{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-61908 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-61908 is a low-severity vulnerability in cyrusimap Cyrus IMAP, published on 9 Sep 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-61908 and fix it if it is affected.\n\nWhat it is: CVE-2026-61908 is a low-severity vulnerability in cyrusimap Cyrus IMAP, published on 9 Sep 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-61908 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-61908/ (Markdown: https://insights.sbomify.com/CVE-2026-61908/index.md)","id":"CVE-2026-61908","markdown":"https://insights.sbomify.com/CVE-2026-61908/index.md","name":"CVE-2026-61908","record":{"aliases":["DEBIAN-CVE-2026-61908","GHSA-2x93-wv63-897r","UBUNTU-CVE-2026-61908"],"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 adjacent heap memory by exploiting an out-of-bounds index in JMAP email-header blob IDs.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"imap","vendor":"cyrus"}],"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-125","name":"Out-of-bounds Read"}],"description":"An issue was discovered in Cyrus IMAP before 3.12.4. A JMAP email-header blob ID can reference an out-of-bounds index. An authenticated user could attempt to download a crafted JMAP blob ID of the form H\u003cemailid\u003e-\u003cindex\u003e, which could read past the end of the internal blob_headers array during download, exposing adjacent heap memory.","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-61908","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Missing authorization in Cyrus IMAP","id":"CVE-2026-61909"},"packages":[],"prev":{"headline":"Missing authorization in Cyrus IMAP","id":"CVE-2026-61907"},"products":["Cyrus IMAP"],"published":"2026-09-09","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2019-18928","kev_date_added":null,"published":"2019-11-15"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2017-14230","kev_date_added":null,"published":"2017-09-10"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2021-33582","kev_date_added":null,"published":"2021-09-01"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2015-8076","kev_date_added":null,"published":"2015-12-03"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2015-8077","kev_date_added":null,"published":"2015-12-03"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2015-8078","kev_date_added":null,"published":"2015-12-03"},{"cvss_score":4.3,"headline":"Information disclosure in Cyrus IMAP","id":"CVE-2026-61911","kev_date_added":null,"published":"2026-09-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-10","vendors":["cyrusimap"]},"summary":"An authenticated user can read adjacent heap memory by exploiting an out-of-bounds index in JMAP email-header blob IDs.","url":"https://insights.sbomify.com/CVE-2026-61908/"}