{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35903 exists.","fix":"No fix has been published for CVE-2026-35903 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-35903 is a critical authentication bypass vulnerability in n/a, published on 27 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-35903 and fix it if it is affected.\n\nWhat it is: CVE-2026-35903 is a critical authentication bypass vulnerability in n/a, published on 27 Apr 2026. 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-2026-35903 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-2026-35903/ (Markdown: https://insights.sbomify.com/CVE-2026-35903/index.md)","id":"CVE-2026-35903","markdown":"https://insights.sbomify.com/CVE-2026-35903/index.md","name":"CVE-2026-35903","record":{"aliases":["GHSA-qcq4-vpjf-wxhh"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"IP camera","requires_auth":"none","summary":"Attackers can bypass RTSP authentication by reusing session parameters, allowing unauthorized control of MERCURY IP cameras.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mipc252w_firmware","vendor":"mercurycom"}],"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-287","name":"Improper Authentication"}],"description":"MERCURY MIPC252W IP camera 1.0.5 Build 230306 Rel.79931n contains an improper authentication vulnerability in the RTSP service. After successful Digest authentication in an initial DESCRIBE request, the device does not verify the Digest response parameter in subsequent RTSP requests within the same session. As a result, RTSP methods such as SETUP, PLAY, and TEARDOWN can be processed even when the Authorization header contains an empty or invalid response value, as long as the nonce and session identifier correspond to a previously authenticated session. This allows an attacker with network access to reuse session parameters and issue unauthorized RTSP control commands without computing a valid Digest response.","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":"Auth bypass in n/a","id":"CVE-2026-35903","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2026-35904"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2026-35902"},"products":["n/a"],"published":"2026-04-27","related":[{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2026-31256","kev_date_added":null,"published":"2026-04-27"},{"cvss_score":6.2,"headline":"Denial of service in n/a","id":"CVE-2026-35902","kev_date_added":null,"published":"2026-04-27"},{"cvss_score":4.4,"headline":"Denial of service in n/a","id":"CVE-2026-35901","kev_date_added":null,"published":"2026-04-27"}],"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-04-28","vendors":["n/a"]},"summary":"Attackers can bypass RTSP authentication by reusing session parameters, allowing unauthorized control of MERCURY IP cameras.","url":"https://insights.sbomify.com/CVE-2026-35903/"}