{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54573 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54573 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54573 is a medium-severity authentication bypass vulnerability in outline, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54573 and fix it if it is affected.\n\nWhat it is: CVE-2026-54573 is a medium-severity authentication bypass vulnerability in outline, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54573 in the wild and no public exploit code.\n\nAffected product: outline. 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-54573/ (Markdown: https://insights.sbomify.com/CVE-2026-54573/index.md)","id":"CVE-2026-54573","markdown":"https://insights.sbomify.com/CVE-2026-54573/index.md","name":"CVE-2026-54573","record":{"aliases":["GHSA-5x79-rj4g-qrh8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Outline documentation service","requires_auth":"low_privilege","summary":"Attackers can bypass API key scope restrictions by appending fragments to URLs, allowing unauthorized access to restricted endpoints and privilege escalation.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Outline is a service that allows for collaborative documentation. Prior to 1.8.0, the AuthenticationHelper.canAccess function uses ctx.originalUrl to verify if an API key or OAuth token has the required scopes for a request. It extracts the resource by splitting the URL by / and taking the last segment. However, it fails to strip the URL fragment (#). Because Koa's router uses ctx.path (which strips the fragment) for routing, an attacker can append a fragment containing a permitted path (e.g., #foo/api/documents.info) to a restricted endpoint (e.g., /api/documents.create). The router will route the request to the restricted endpoint, but canAccess will evaluate the permitted path in the fragment, bypassing the API key scope restrictions and allowing privilege escalation. This vulnerability is fixed in 1.8.0.","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":"Authorization Bypass in API Key/OAuth Scopes via Path Parsing Discrepancy","id":"CVE-2026-54573","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"`proot-distro install` has a Symlink Escape (Arbitrary Host File Write) via Malicious Tar Archive","id":"CVE-2026-54574"},"packages":[],"prev":{"headline":"rclone: Unvalidated symlink target in local `--links` — arbitrary file write from an untrusted remote","id":"CVE-2026-54572"},"products":["outline"],"published":"2026-06-25","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)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-26","vendors":["outline"]},"summary":"Attackers can bypass API key scope restrictions by appending fragments to URLs, allowing unauthorized access to restricted endpoints and privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-54573/"}