{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-4820 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-4820 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4820 is a medium-severity vulnerability in IBM Maximo Application Suite, published on 1 Apr 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-4820 and fix it if it is affected.\n\nWhat it is: CVE-2026-4820 is a medium-severity vulnerability in IBM Maximo Application Suite, published on 1 Apr 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: There is no known exploitation of CVE-2026-4820 in the wild and no public exploit code.\n\nAffected product: IBM Maximo Application Suite. 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-4820/ (Markdown: https://insights.sbomify.com/CVE-2026-4820/index.md)","id":"CVE-2026-4820","markdown":"https://insights.sbomify.com/CVE-2026-4820/index.md","name":"CVE-2026-4820","record":{"aliases":["GHSA-7cvp-jxjh-qvvf"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Maximo Application Suite","requires_auth":"none","summary":"Attackers can steal session cookies via insecure HTTP links, potentially leading to account takeover in IBM Maximo Application Suite.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"maximo_application_suite","vendor":"ibm"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"},{"id":"CWE-614","name":"Sensitive Cookie in HTTPS Session Without 'Secure' Attribute"}],"description":"IBM Maximo Application Suite 9.1, 9.0, 8.11, and 8.10 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic.","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":"IBM Maximo Application Suite was vulnerable to because Cookie ltpatoken2_\u003cworkspace_name\u003e was not set with secure flag","id":"CVE-2026-4820","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as it was published in error.","id":"CVE-2026-4821"},"packages":[],"prev":{"headline":"Search Guard audit logs can contain under certain conditions user credentials","id":"CVE-2026-4819"},"products":["Maximo Application Suite"],"published":"2026-04-01","related":[{"cvss_score":9.8,"headline":"There is a vulnerability in the IBM Maximo Manage application in IBM Maximo Application Suite for Cognos Analytics","id":"CVE-2025-36386","kev_date_added":null,"published":"2025-10-28"},{"cvss_score":8.2,"headline":"IBM Maximo Application Suite XML external entity injection","id":"CVE-2024-27266","kev_date_added":null,"published":"2024-03-14"},{"cvss_score":7.5,"headline":"IBM Maximo Application Suite privilege escalation","id":"CVE-2025-2898","kev_date_added":null,"published":"2025-05-06"},{"cvss_score":7.5,"headline":"IBM Maximo Application Suite information disclosure","id":"CVE-2024-22328","kev_date_added":null,"published":"2024-04-06"},{"cvss_score":6.5,"headline":"IBM Maximo Application Suite improper access control","id":"CVE-2023-43037","kev_date_added":null,"published":"2025-04-10"},{"cvss_score":6.4,"headline":"Maximo Asset Management cross-site scripting","id":"CVE-2023-38723","kev_date_added":null,"published":"2024-03-13"},{"cvss_score":6.4,"headline":"IBM Maximo Asset Management cross-site scripting","id":"CVE-2022-35645","kev_date_added":null,"published":"2023-03-02"}],"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-04-02","vendors":["IBM"]},"summary":"Attackers can steal session cookies via insecure HTTP links, potentially leading to account takeover in IBM Maximo Application Suite.","url":"https://insights.sbomify.com/CVE-2026-4820/"}