{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-0326 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-0326 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-0326 is a vulnerability in WSO2 Carbon OAuth, published on 21 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2025-0326 and fix it if it is affected.\n\nWhat it is: CVE-2025-0326 is a vulnerability in WSO2 Carbon OAuth, published on 21 Oct 2026. \nExploitation: There is no known exploitation of CVE-2025-0326 in the wild and no public exploit code.\n\nAffected product: WSO2 Carbon OAuth. 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-0326/ (Markdown: https://insights.sbomify.com/CVE-2025-0326/index.md)","id":"CVE-2025-0326","markdown":"https://insights.sbomify.com/CVE-2025-0326/index.md","name":"CVE-2025-0326","record":{"aliases":["GHSA-6mrj-7qf3-gjqc"],"analysis":null,"analysis_generated_by":null,"assigner":"WSO2","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"The system fails to invalidate existing access tokens associated with sub-organization users during sensitive account management operations such as password reset, role change, or sub-organization disablement. This oversight allows previously issued tokens to remain active even after the user's access context has been modified or revoked through administrative actions.\n\nThe identified issue could lead to unauthorized access by a malicious actor, but only when all of the following conditions are met: previously issued access tokens remain active, and these tokens have been exposed to malicious actors.","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":"Improper Token Revocation in WSO2 Identity Server Allows Unauthorized Access","id":"CVE-2025-0326","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in EcoStruxure Process Expert","id":"CVE-2025-0327"},"packages":[],"prev":{"headline":"Denial of service in AXIS OS","id":"CVE-2025-0325"},"products":["WSO2 Carbon OAuth","WSO2 Identity Server"],"published":"2026-10-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["WSO2"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-0326/"}