{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-22907 exists.","fix":"No fix has been published for CVE-2025-22907 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-22907 is a critical memory corruption vulnerability in n/a, published on 16 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-22907 and fix it if it is affected.\n\nWhat it is: CVE-2025-22907 is a critical memory corruption vulnerability in n/a, published on 16 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-22907 exists.\n\nAffected product: n/a. 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-22907/ (Markdown: https://insights.sbomify.com/CVE-2025-22907/index.md)","id":"CVE-2025-22907","markdown":"https://insights.sbomify.com/CVE-2025-22907/index.md","name":"CVE-2025-22907","record":{"aliases":["GHSA-vcjx-5pw3-c283"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"RE11S firmware","requires_auth":"none","summary":"A stack overflow in the RE11S firmware allows attackers to execute arbitrary code or cause a denial of service via the selSSID parameter.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"re11s_firmware","vendor":"edimax"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"RE11S v1.11 was discovered to contain a stack overflow via the selSSID parameter in the formWlSiteSurvey function.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2025-22907","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2025-22911"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2025-22906"},"products":["n/a"],"published":"2025-01-16","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-22904","kev_date_added":null,"published":"2025-01-16"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2025-22905","kev_date_added":null,"published":"2025-01-16"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2025-22906","kev_date_added":null,"published":"2025-01-16"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2025-22912","kev_date_added":null,"published":"2025-01-16"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-22913","kev_date_added":null,"published":"2025-01-16"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-22916","kev_date_added":null,"published":"2025-01-16"}],"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-07","vendors":["n/a"]},"summary":"A stack overflow in the RE11S firmware allows attackers to execute arbitrary code or cause a denial of service via the selSSID parameter.","url":"https://insights.sbomify.com/CVE-2025-22907/"}