{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-10079 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-10079 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-10079 is a high-severity vulnerability in Red Hat Advanced Cluster Security 4, published on 31 Jul 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-10079 and fix it if it is affected.\n\nWhat it is: CVE-2026-10079 is a high-severity vulnerability in Red Hat Advanced Cluster Security 4, published on 31 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-10079 in the wild and no public exploit code.\n\nAffected product: Red Hat Advanced Cluster Security 4. 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-10079/ (Markdown: https://insights.sbomify.com/CVE-2026-10079/index.md)","id":"CVE-2026-10079","markdown":"https://insights.sbomify.com/CVE-2026-10079/index.md","name":"CVE-2026-10079","record":{"aliases":["GHSA-vq3f-pc8h-pv73"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes security platform","requires_auth":"low_privilege","summary":"Attackers can bypass deploy-time policy enforcement and visibility in Red Hat Advanced Cluster Security by injecting null labels into Kubernetes deployments.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"A flaw was found in Red Hat Advanced Cluster Security for Kubernetes (RHACS). When processing Kubernetes Deployments, ACS replaces deployment identity metadata based on the openshift.io/encoded-deployment-config label. A user with permission to create Deployments can set this label to \"null\", causing ACS to treat the workload as having empty UID, name and labels and namespace \"default\". This bypasses deploy-time policy detection and enforcement visibility, prevents correct persistence in Central and breaks violation reporting and compliance correlation for the affected deployment.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Stackrox: stackrox: deploy-time policy enforcement and visibility bypass via label injection","id":"CVE-2026-10079","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Boards plugin panics on WebSocket command with non-string field types","id":"CVE-2026-10080"},"packages":[],"prev":{"headline":"Quay/config-tool: quay/config-tool: gitlab oauth client_secret exposed in url querystring","id":"CVE-2026-10078"},"products":["Red Hat Advanced Cluster Security 4"],"published":"2026-07-31","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-07-31","vendors":["Red Hat"]},"summary":"Attackers can bypass deploy-time policy enforcement and visibility in Red Hat Advanced Cluster Security by injecting null labels into Kubernetes deployments.","url":"https://insights.sbomify.com/CVE-2026-10079/"}