{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123011 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-123011 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-123011 is a medium-severity vulnerability in STMicroelectronics st-mems-android-linux-sensors-hal, published on 5 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-123011 and fix it if it is affected.\n\nWhat it is: CVE-2026-123011 is a medium-severity vulnerability in STMicroelectronics st-mems-android-linux-sensors-hal, published on 5 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-123011 in the wild and no public exploit code.\n\nAffected product: STMicroelectronics st-mems-android-linux-sensors-hal. 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-123011/ (Markdown: https://insights.sbomify.com/CVE-2026-123011/index.md)","id":"CVE-2026-123011","markdown":"https://insights.sbomify.com/CVE-2026-123011/index.md","name":"CVE-2026-123011","record":{"aliases":["GHSA-hxxf-v8p5-g347"],"analysis":null,"analysis_generated_by":null,"assigner":"mitre","cpe":[],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-1284","name":"Improper Validation of Specified Quantity in Input"}],"description":"STMicroelectronics st-mems-android-linux-sensors-hal before 7bdf334 does not check whether the allowed number of channels is exceeded.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"STMicroelectronics st-mems-android-linux-sensors-hal before 7bdf334 does not check whether the allowed number of channels is exceeded.","id":"CVE-2026-123011","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"In Gogs 0.14.3, the Git Smart HTTP authorization layer in internal/route/repo/http.go allows a push when only read access was intended, a di","id":"CVE-2026-123012"},"nickname":null,"packages":[],"prev":{"headline":"@twilio-labs/netlify-okta-auth through 1.0.2 relies on an unverified iss claim.","id":"CVE-2026-123010"},"products":["st-mems-android-linux-sensors-hal"],"published":"2026-11-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-11-09","vendors":["STMicroelectronics"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-123011/"}