{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-53895 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-53895 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-53895 is a high-severity missing authorization vulnerability in zitadel, published on 15 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-53895 and fix it if it is affected.\n\nWhat it is: CVE-2025-53895 is a high-severity missing authorization vulnerability in zitadel, published on 15 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-53895 in the wild and no public exploit code.\n\nAffected product: zitadel. 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-2025-53895/ (Markdown: https://insights.sbomify.com/CVE-2025-53895/index.md)","id":"CVE-2025-53895","markdown":"https://insights.sbomify.com/CVE-2025-53895/index.md","name":"CVE-2025-53895","record":{"aliases":["GHSA-6c5p-6www-pcmr"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Identity management system","requires_auth":"low_privilege","summary":"Authenticated users can hijack sessions by updating them without permission checks, enabling impersonation and access to sensitive resources.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"zitadel","vendor":"zitadel"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-384","name":"Session Fixation"}],"description":"ZITADEL is an open source identity management system. Starting in version 2.53.0 and prior to versions 4.0.0-rc.2, 3.3.2, 2.71.13, and 2.70.14, vulnerability in ZITADEL's session management API allows any authenticated user to update a session if they know its ID, due to a missing permission check. This flaw enables session hijacking, allowing an attacker to impersonate another user and access sensitive resources. Versions prior to `2.53.0` are not affected, as they required the session token for updates. Versions 4.0.0-rc.2, 3.3.2, 2.71.13, and 2.70.14 fix the issue.","ecosystems":[],"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":"ZITADEL has broken authN and authZ in session API and resulting session tokens","id":"CVE-2025-53895","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"Kiteworks MFT is vulnerable to Insufficient Session Expiration","id":"CVE-2025-53896"},"packages":[],"prev":{"headline":"File Browser Vulnerable to Uncontrolled Memory Consumption Due to Oversized File Processing","id":"CVE-2025-53893"},"products":["zitadel"],"published":"2025-07-15","related":[{"cvss_score":9.3,"headline":"ZITADEL: 1-Click Account Takeover via XSS in /saml-post Endpoint","id":"CVE-2026-29191","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":9.3,"headline":"ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login","id":"CVE-2025-67494","kev_date_added":null,"published":"2025-12-09"},{"cvss_score":9,"headline":"IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations","id":"CVE-2025-27507","kev_date_added":null,"published":"2025-03-04"},{"cvss_score":8.7,"headline":"Zitadel Bypass Second Authentication Factor","id":"CVE-2025-64103","kev_date_added":null,"published":"2025-10-29"},{"cvss_score":8.7,"headline":"Zitadel Expired JWT Keys Usable for Authorization Grants","id":"CVE-2025-31123","kev_date_added":null,"published":"2025-03-31"},{"cvss_score":8.7,"headline":"ZITADEL Improper Content-Type Validation Leads to Account Takeover via Stored XSS + CSP Bypass","id":"CVE-2024-29891","kev_date_added":null,"published":"2024-03-27"},{"cvss_score":8.7,"headline":"XSS with User Avatar image in ZITADEL","id":"CVE-2023-46238","kev_date_added":null,"published":"2023-10-26"}],"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":"total"},"state":"PUBLISHED","updated":"2025-07-15","vendors":["zitadel"]},"summary":"Authenticated users can hijack sessions by updating them without permission checks, enabling impersonation and access to sensitive resources.","url":"https://insights.sbomify.com/CVE-2025-53895/"}