{"answers":{"affected":"2 open source packages ship an affected version, including kimai/kimai.","exploited":"There is no known exploitation of CVE-2026-80200 in the wild and no public exploit code.","fix":"Upgrade kimai/kimai to 2.53.0 or later.","what":"CVE-2026-80200 is a medium-severity vulnerability in kimai, published on 25 Aug 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-80200 and fix it if it is affected.\n\nWhat it is: CVE-2026-80200 is a medium-severity vulnerability in kimai, published on 25 Aug 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-80200 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- kimai/kimai (Packagist): affected all versions; fixed in 2.53.0\n- kimai/kimai (Packagist): affected all versions; fixed in 2.53.0\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-80200/ (Markdown: https://insights.sbomify.com/CVE-2026-80200/index.md)","id":"CVE-2026-80200","markdown":"https://insights.sbomify.com/CVE-2026-80200/index.md","name":"CVE-2026-80200","record":{"aliases":["GHSA-3jp4-mhh4-gcgr","GHSA-wv9h-9jv8-rqm9"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Kimai time tracking","requires_auth":"none","summary":"Attackers with IdP access can redirect authenticated Kimai users to malicious sites via unvalidated RelayState parameters, enabling phishing or credential theft.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"Kimai before 2.53.0 contains an open redirect vulnerability in the SAML authentication success handler that accepts unvalidated RelayState POST parameters as redirect destinations. Attackers with IdP access can supply malicious RelayState values to redirect authenticated users to attacker-controlled URLs for credential theft or phishing attacks.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Kimai before 2.53.0 Open Redirect via RelayState","id":"CVE-2026-80200","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"open_redirect","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Kimai before 2.53.0 API Token Leakage via Invoice Template","id":"CVE-2026-80201"},"packages":[{"ecosystem":"Packagist","fixed":["2.53.0"],"introduced":["0"],"last_affected":[],"package":"kimai/kimai","purl":null,"source":"GHSA-3jp4-mhh4-gcgr"},{"ecosystem":"Packagist","fixed":["2.53.0"],"introduced":["0"],"last_affected":[],"package":"kimai/kimai","purl":"pkg:composer/kimai/kimai","source":"GHSA-3jp4-mhh4-gcgr"}],"prev":{"headline":"Kimai before 2.54.0 Username Enumeration via Timing Oracle","id":"CVE-2026-80199"},"products":["kimai"],"published":"2026-08-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-10-08","vendors":["kimai"]},"summary":"Attackers with IdP access can redirect authenticated Kimai users to malicious sites via unvalidated RelayState parameters, enabling phishing or credential theft.","url":"https://insights.sbomify.com/CVE-2026-80200/"}