{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-26510 exists.","fix":"No fix has been published for CVE-2022-26510 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-26510 is a critical missing authorization vulnerability in InHand Networks InRouter302, published on 12 May 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-26510 and fix it if it is affected.\n\nWhat it is: CVE-2022-26510 is a critical missing authorization vulnerability in InHand Networks InRouter302, published on 12 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-26510 exists.\n\nAffected product: InHand Networks InRouter302. 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-2022-26510/ (Markdown: https://insights.sbomify.com/CVE-2022-26510/index.md)","id":"CVE-2022-26510","markdown":"https://insights.sbomify.com/CVE-2022-26510/index.md","name":"CVE-2022-26510","record":{"aliases":["GHSA-567v-8x5m-wxxw"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"InHand Networks router","requires_auth":"low_privilege","summary":"An attacker can trigger a firmware update via a crafted HTTP request due to missing authorization checks, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"ir302_firmware","vendor":"inhandnetworks"}],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"A firmware update vulnerability exists in the iburn firmware checks functionality of InHand Networks InRouter302 V3.5.37. A specially-crafted HTTP request can lead to firmware update. An attacker can send a sequence of 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":"weaponised"},"has_fix":null,"headline":"Missing authorization in InRouter302","id":"CVE-2022-26510","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Other in WPS Presentation","id":"CVE-2022-26511"},"packages":[],"prev":{"headline":"Information disclosure in Intel(R) SGX SDK software","id":"CVE-2022-26509"},"products":["InRouter302"],"published":"2022-05-12","related":[{"cvss_score":9.9,"headline":"Command injection in InRouter302","id":"CVE-2022-25995","kev_date_added":null,"published":"2022-05-12"},{"cvss_score":9.9,"headline":"Command injection in InRouter302","id":"CVE-2022-26042","kev_date_added":null,"published":"2022-05-12"},{"cvss_score":9.9,"headline":"Command injection in InRouter302","id":"CVE-2022-26075","kev_date_added":null,"published":"2022-05-12"},{"cvss_score":9.9,"headline":"Command injection in InRouter302","id":"CVE-2022-26085","kev_date_added":null,"published":"2022-05-12"},{"cvss_score":9.9,"headline":"Command injection in InRouter302","id":"CVE-2022-26420","kev_date_added":null,"published":"2022-05-12"},{"cvss_score":9.9,"headline":"Command injection in InRouter302","id":"CVE-2022-26518","kev_date_added":null,"published":"2022-05-12"}],"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["InHand Networks"]},"summary":"An attacker can trigger a firmware update via a crafted HTTP request due to missing authorization checks, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2022-26510/"}