{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2024-49394 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2024-49394 is a medium-severity vulnerability in Redhat Enterprise Linux, published on 12 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-49394 and fix it if it is affected.\n\nWhat it is: CVE-2024-49394 is a medium-severity vulnerability in Redhat Enterprise Linux, published on 12 Nov 2024. 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-2024-49394 in the wild and no public exploit code.\n\nAffected product: Redhat Enterprise Linux. 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-2024-49394/ (Markdown: https://insights.sbomify.com/CVE-2024-49394/index.md)","id":"CVE-2024-49394","markdown":"https://insights.sbomify.com/CVE-2024-49394/index.md","name":"CVE-2024-49394","record":{"aliases":["CLSA-2026-1783434809","CLSA-2026-1783436433","DEBIAN-CVE-2024-49394","GHSA-q998-8jff-x3rg","UBUNTU-CVE-2024-49394"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Mutt email client","requires_auth":"none","summary":"Attackers can bypass cryptographic signing protections in Mutt and Neomutt by reusing unencrypted signed emails to impersonate senders.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"mutt","vendor":"mutt"},{"product":"neomutt","vendor":"neomutt"},{"product":"enterprise_linux","vendor":"redhat"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"In mutt and neomutt the In-Reply-To email header field is not protected by cryptographic signing which allows an attacker to reuse an unencrypted but signed email message to impersonate the original sender.","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":"Mutt: neomutt: in-reply-to email header field it not protected by cryptograpic signing","id":"CVE-2024-49394","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"redhat:enterprise_linux","products":["redhat:enterprise_linux"],"type":"security_feature_bypass","year":"2024"},"n_packages":0,"n_references":5,"next":{"headline":"Mutt: neomutt: bcc email header field is indirectly leaked by cryptographic info block","id":"CVE-2024-49395"},"packages":[],"prev":{"headline":"Mutt: neomutt: to and cc email header fields are not protected by cryptographic signing","id":"CVE-2024-49393"},"products":["Red Hat Enterprise Linux 7","Red Hat Enterprise Linux 8","Red Hat Enterprise Linux 9"],"published":"2024-11-12","related":[{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2021-32055","kev_date_added":null,"published":"2021-05-05"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2006-3242","kev_date_added":null,"published":"2006-06-27"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2005-2642","kev_date_added":null,"published":"2005-08-21"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2004-0078","kev_date_added":null,"published":"2004-09-01"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2003-0299","kev_date_added":null,"published":"2003-05-15"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2003-0167","kev_date_added":null,"published":"2003-03-29"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2003-0140","kev_date_added":null,"published":"2003-03-21"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-26","vendors":["Red Hat"]},"summary":"Attackers can bypass cryptographic signing protections in Mutt and Neomutt by reusing unencrypted signed emails to impersonate senders.","url":"https://insights.sbomify.com/CVE-2024-49394/"}