{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6272 exists.","fix":"No fix has been published for CVE-2026-6272 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6272 is a high-severity missing authorization vulnerability in Eclipse KUKSA - Databroker, published on 24 Apr 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-6272 and fix it if it is affected.\n\nWhat it is: CVE-2026-6272 is a high-severity missing authorization vulnerability in Eclipse KUKSA - Databroker, published on 24 Apr 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-6272 exists.\n\nAffected product: Eclipse KUKSA - Databroker. 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-6272/ (Markdown: https://insights.sbomify.com/CVE-2026-6272/index.md)","id":"CVE-2026-6272","markdown":"https://insights.sbomify.com/CVE-2026-6272/index.md","name":"CVE-2026-6272","record":{"aliases":["GHSA-66v8-c34p-jmrm"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Eclipse KUKSA Databroker","requires_auth":"low_privilege","summary":"Attackers with read-only access can register as signal providers to inject forged data into the Eclipse KUKSA Databroker, compromising data integrity.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"A client holding only a read JWT scope can still register itself as a signal provider through the production kuksa.val.v2 OpenProviderStream API by sending ProvideSignalRequest.\n\n1. Obtain any valid token with only read scope.\n2. Connect to the normal production gRPC API (kuksa.val.v2).\n3. Open OpenProviderStream.\n4. Send ProvideSignalRequest for a target signal ID.\n5. Wait for the broker to forward GetProviderValueRequest.\n6. Reply with attacker-controlled GetProviderValueResponse.\n7. Other clients performing GetValue / GetValues for that signal receive forged data.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Missing authorization in Eclipse KUKSA - Databroker","id":"CVE-2026-6272","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Authentication Bypass in DTS Electronics' Redline WR3200","id":"CVE-2026-6274"},"packages":[],"prev":{"headline":"Career Section \u003c= 1.7 - Unauthenticated Arbitrary File Upload","id":"CVE-2026-6271"},"products":["Eclipse KUKSA - Databroker"],"published":"2026-04-24","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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-24","vendors":["Eclipse Foundation"]},"summary":"Attackers with read-only access can register as signal providers to inject forged data into the Eclipse KUKSA Databroker, compromising data integrity.","url":"https://insights.sbomify.com/CVE-2026-6272/"}