{"answers":{"affected":"4 open source packages ship an affected version, including laravel/framework.","exploited":"There is no known exploitation of GHSA-crmm-hgp2-wgrp in the wild and no public exploit code.","fix":"Upgrade laravel/framework to a fixed version for your release line: 12.61.1 or 13.12.0.","what":"GHSA-crmm-hgp2-wgrp is a vulnerability in laravel/framework, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-crmm-hgp2-wgrp and fix it if it is affected.\n\nWhat it is: GHSA-crmm-hgp2-wgrp is a vulnerability in laravel/framework, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-crmm-hgp2-wgrp in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- laravel/framework (Packagist): affected all versions; fixed in 12.61.1\n- laravel/framework (Packagist): affected all versions; fixed in 12.61.1\n- laravel/framework (Packagist): affected from 13.0.0; fixed in 13.12.0\n- laravel/framework (Packagist): affected from 13.0.0; fixed in 13.12.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/GHSA-crmm-hgp2-wgrp/ (Markdown: https://insights.sbomify.com/GHSA-crmm-hgp2-wgrp/index.md)","id":"GHSA-crmm-hgp2-wgrp","markdown":"https://insights.sbomify.com/GHSA-crmm-hgp2-wgrp/index.md","name":"GHSA-crmm-hgp2-wgrp","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Laravel Framework","requires_auth":"none","summary":"Attackers can bypass expiration checks on signed URLs and potentially write to unintended locations due to path parsing ambiguities in Laravel's local filesystem driver.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"A vulnerability in Laravel's local filesystem driver allows temporary signed URLs to be parsed ambiguously, potentially misrouting requests and bypassing expiration enforcement.\n\nUnder certain conditions, a generated temporary signed URL can be interpreted differently by the server than intended at signing time. This may cause requests to resolve to an unintended resource, and can prevent expiration from being enforced, allowing expired URLs to remain valid indefinitely.\n\n### Impact\n- Expired temporary URLs may continue to be accepted\n- Requests may resolve to a different resource than the one that was signed\n- The upload variant may allow writes to reach an unintended destination","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Laravel Framework: Temporary Signed URL Path Confusion","id":"GHSA-crmm-hgp2-wgrp","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["12.61.1"],"introduced":["0"],"last_affected":[],"package":"laravel/framework","purl":null,"source":"GHSA-crmm-hgp2-wgrp"},{"ecosystem":"Packagist","fixed":["12.61.1"],"introduced":["0"],"last_affected":[],"package":"laravel/framework","purl":"pkg:composer/laravel/framework","source":"GHSA-crmm-hgp2-wgrp"},{"ecosystem":"Packagist","fixed":["13.12.0"],"introduced":["13.0.0"],"last_affected":[],"package":"laravel/framework","purl":null,"source":"GHSA-crmm-hgp2-wgrp"},{"ecosystem":"Packagist","fixed":["13.12.0"],"introduced":["13.0.0"],"last_affected":[],"package":"laravel/framework","purl":"pkg:composer/laravel/framework","source":"GHSA-crmm-hgp2-wgrp"}],"products":null,"published":"2026-06-17","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can bypass expiration checks on signed URLs and potentially write to unintended locations due to path parsing ambiguities in Laravel's local filesystem driver.","url":"https://insights.sbomify.com/GHSA-crmm-hgp2-wgrp/"}