{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-26091 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-26091 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-26091 is a medium-severity vulnerability in Fortinet FortiMail, published on 24 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-26091 and fix it if it is affected.\n\nWhat it is: CVE-2021-26091 is a medium-severity vulnerability in Fortinet FortiMail, published on 24 Mar 2025. 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-2021-26091 in the wild and no public exploit code.\n\nAffected product: Fortinet FortiMail. 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-2021-26091/ (Markdown: https://insights.sbomify.com/CVE-2021-26091/index.md)","id":"CVE-2021-26091","markdown":"https://insights.sbomify.com/CVE-2021-26091/index.md","name":"CVE-2021-26091","record":{"aliases":["GHSA-pmxq-4hqc-9hr4"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"FortiMail email security","requires_auth":"none","summary":"An unauthenticated attacker can infer authentication tokens due to weak randomness, allowing them to reset user credentials and take over accounts.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortimail","vendor":"fortinet"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:U/RC:C","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"A use of a cryptographically weak pseudo-random number generator vulnerability in the authenticator of the Identity Based Encryption service of FortiMail 6.4.0 through 6.4.4, and 6.2.0 through 6.2.7 may allow an unauthenticated attacker to infer parts of users authentication tokens and reset their credentials.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Weak cryptography in FortiMail","id":"CVE-2021-26091","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in Fortinet FortiOS, FortiProxy","id":"CVE-2021-26092"},"packages":[],"prev":{"headline":"Denial of service in Fortinet FortiMail","id":"CVE-2021-26090"},"products":["FortiMail"],"published":"2025-03-24","related":[{"cvss_score":9.8,"headline":"Fortinet FortiMail Path Traversal","id":"CVE-2026-104286","kev_date_added":"2026-10-01","published":"2026-10-01"},{"cvss_score":9.8,"headline":"Auth bypass in Fortinet FortiMail","id":"CVE-2021-36166","kev_date_added":null,"published":"2022-03-01"},{"cvss_score":9.8,"headline":"SQL injection in Fortinet FortiMail","id":"CVE-2021-24007","kev_date_added":null,"published":"2021-07-09"},{"cvss_score":9.8,"headline":"Auth bypass in FortiMail","id":"CVE-2020-9294","kev_date_added":null,"published":"2020-04-27"},{"cvss_score":9,"headline":"Auth bypass in FortiMail","id":"CVE-2023-47539","kev_date_added":null,"published":"2025-03-18"},{"cvss_score":8.8,"headline":"Path traversal in Fortinet FortiMail","id":"CVE-2021-24013","kev_date_added":null,"published":"2021-07-12"},{"cvss_score":8.8,"headline":"Memory corruption in Fortinet FortiMail","id":"CVE-2021-22129","kev_date_added":null,"published":"2021-07-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":"2025-03-31","vendors":["Fortinet"]},"summary":"An unauthenticated attacker can infer authentication tokens due to weak randomness, allowing them to reset user credentials and take over accounts.","url":"https://insights.sbomify.com/CVE-2021-26091/"}