{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57920 exists.","fix":"No fix has been published for CVE-2026-57920 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-57920 is a high-severity vulnerability in Peplink InControl, published on 26 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-57920 and fix it if it is affected.\n\nWhat it is: CVE-2026-57920 is a high-severity vulnerability in Peplink InControl, published on 26 Jun 2026. 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-2026-57920 exists.\n\nAffected product: Peplink InControl. 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-57920/ (Markdown: https://insights.sbomify.com/CVE-2026-57920/index.md)","id":"CVE-2026-57920","markdown":"https://insights.sbomify.com/CVE-2026-57920/index.md","name":"CVE-2026-57920","record":{"aliases":["GHSA-69xh-mqwf-cxv2"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Peplink InControl 2","requires_auth":"low_privilege","summary":"Attackers can bypass access-control rules on specific REST endpoints using semicolons, potentially accessing restricted resources in Peplink InControl 2.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"intcontrol_2","vendor":"peplink"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-551","name":"Incorrect Behavior Order: Authorization Before Parsing and Canonicalization"}],"description":"Peplink InControl 2 through 2.14.2 before 2026-06-03 allows use of a semicolon to bypass access-control rules for certain /rest/o/{orgId} endpoints.","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":"Security feature bypass in InControl","id":"CVE-2026-57920","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in YouTrack","id":"CVE-2026-57921"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2026-57919"},"products":["InControl"],"published":"2026-06-26","related":[],"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":"partial"},"state":"PUBLISHED","updated":"2026-06-26","vendors":["Peplink"]},"summary":"Attackers can bypass access-control rules on specific REST endpoints using semicolons, potentially accessing restricted resources in Peplink InControl 2.","url":"https://insights.sbomify.com/CVE-2026-57920/"}