{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-48826 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-48826 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-48826 is a high-severity memory corruption vulnerability in Planet WGR-500, published on 7 Oct 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-48826 and fix it if it is affected.\n\nWhat it is: CVE-2025-48826 is a high-severity memory corruption vulnerability in Planet WGR-500, published on 7 Oct 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-48826 in the wild and no public exploit code.\n\nAffected product: Planet WGR-500. 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-48826/ (Markdown: https://insights.sbomify.com/CVE-2025-48826/index.md)","id":"CVE-2025-48826","markdown":"https://insights.sbomify.com/CVE-2025-48826/index.md","name":"CVE-2025-48826","record":{"aliases":["GHSA-9vmf-4m6v-4cmv"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Planet WGR-500 router","requires_auth":"low_privilege","summary":"A format string vulnerability in the Planet WGR-500 router allows attackers to cause memory corruption via crafted HTTP requests.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"wgr-500_firmware","vendor":"planet"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-134","name":"Use of Externally-Controlled Format String"}],"description":"A format string vulnerability exists in the formPingCmd functionality of Planet WGR-500 v1.3411b190912. A specially crafted series of HTTP requests can lead to memory corruption. An attacker can send a series of HTTP requests to trigger this vulnerability.","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":"Memory corruption in WGR-500","id":"CVE-2025-48826","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"vBulletin 5.0.0 through 5.7.5 and 6.0.0 through 6.0.3 allows unauthenticated users to invoke protected API controllers' methods when running","id":"CVE-2025-48827"},"packages":[],"prev":{"headline":"Supply chain in RICOH Streamline NX V3 PC Client","id":"CVE-2025-48825"},"products":["WGR-500"],"published":"2025-10-07","related":[{"cvss_score":8.8,"headline":"Memory corruption in WGR-500","id":"CVE-2025-54399","kev_date_added":null,"published":"2025-10-07"},{"cvss_score":8.8,"headline":"Memory corruption in WGR-500","id":"CVE-2025-54400","kev_date_added":null,"published":"2025-10-07"},{"cvss_score":8.8,"headline":"Memory corruption in WGR-500","id":"CVE-2025-54401","kev_date_added":null,"published":"2025-10-07"},{"cvss_score":8.8,"headline":"Memory corruption in WGR-500","id":"CVE-2025-54402","kev_date_added":null,"published":"2025-10-07"},{"cvss_score":8.8,"headline":"Command injection in WGR-500","id":"CVE-2025-54403","kev_date_added":null,"published":"2025-10-07"},{"cvss_score":8.8,"headline":"Command injection in WGR-500","id":"CVE-2025-54404","kev_date_added":null,"published":"2025-10-07"}],"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-11-03","vendors":["Planet"]},"summary":"A format string vulnerability in the Planet WGR-500 router allows attackers to cause memory corruption via crafted HTTP requests.","url":"https://insights.sbomify.com/CVE-2025-48826/"}