{"answers":{"affected":"","exploited":"There is no known exploitation of SUSE-SU-2026:4112-1 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"SUSE-SU-2026:4112-1 is a vulnerability in libzypp, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for SUSE-SU-2026:4112-1 and fix it if it is affected.\n\nWhat it is: SUSE-SU-2026:4112-1 is a vulnerability in libzypp, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of SUSE-SU-2026:4112-1 in the wild and no public exploit code.\n\nAffected product: libzypp. 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/SUSE-SU-2026-4112-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2026-4112-1/index.md)","id":"SUSE-SU-2026:4112-1","markdown":"https://insights.sbomify.com/SUSE-SU-2026-4112-1/index.md","name":"SUSE-SU-2026:4112-1","record":{"aliases":[],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SUSE package manager","requires_auth":"none","summary":"Attackers can bypass repository signature checks and credential validation in SUSE's libzypp and zypper package managers.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This update for libzypp, zypper fixes the following issues:\n\nSecurity issue fixed:\n\n- invalidating legacy libzypp unsigned-repository cache state [LIBZYPP-LEGACY-CACHE-01] (bsc#1274625).\n- hasCredentials() requires both username AND password to be non-empty (bsc#1273242).\n- GPG Key hints in repoindex.xml require at least a long id to allow auto-import (bsc#1271730).\n\nNon security issues fixed:\n\n- Econf parser adds tags in drop-in files outside any section to [main] (bsc#1272534).\n- libzypp: X-ZYpp-AnonymousId header anomaly (bsc#1268321).\n- Need zypper option to disable services to fix Dockerfile builds in OBS (bsc#1257249).\n- zypper loads repository data and installed packages prior to checking for required arguments (bsc#1274091).\n- Zypper patch doesn't give enough details about conflicts (bsc#1277790).\n- dependency issue for package 'python3-vsts-cd-manager' after starting the upgrade (bsc#1261038).\nChanges for libzypp:\n\n- Update to version 17.38.15:\n\n  - Prevent libgpgme from launching gpg-agents; we don't need them.\n  - defaultLoadSystem: Hand out the ZYpp::Ptr as return value.\n  - Replace popen cat/zcat with solv_xfopen for testcase loaders\n    (fixes #749)\n  - zypp: Improve Testcase Loading for MCP Tools.\n  - spec: Remove useless %bcond visibility_hidden (is always ON in\n    cmake)\n  - zypp.conf: add solver.NoUpdateProvide (default: false) option.\n\nChanges for zypper:\n\n- Update to version 1.14.101.","ecosystems":["SUSE:Linux Enterprise Installer Updates 15 SP6","SUSE:Linux Enterprise Server 15 SP6-LTSS"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Security update for libzypp, zypper","id":"SUSE-SU-2026:4112-1","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"SUSE:Linux Enterprise Installer Updates 15 SP6","fixed":["17.38.15-150600.3.95.1"],"introduced":["0"],"last_affected":[],"package":"libzypp","purl":"pkg:rpm/suse/libzypp\u0026distro=SUSE%20Linux%20Enterprise%20Installer%20Updates%2015%20SP6","source":"SUSE-SU-2026:4112-1"},{"ecosystem":"SUSE:Linux Enterprise Server 15 SP6-LTSS","fixed":["17.38.15-150600.3.95.1"],"introduced":["0"],"last_affected":[],"package":"libzypp","purl":"pkg:rpm/suse/libzypp\u0026distro=SUSE%20Linux%20Enterprise%20Server%2015%20SP6-LTSS","source":"SUSE-SU-2026:4112-1"},{"ecosystem":"SUSE:Linux Enterprise Server 15 SP6-LTSS","fixed":["1.14.101-150600.10.58.1"],"introduced":["0"],"last_affected":[],"package":"zypper","purl":"pkg:rpm/suse/zypper\u0026distro=SUSE%20Linux%20Enterprise%20Server%2015%20SP6-LTSS","source":"SUSE-SU-2026:4112-1"}],"products":null,"published":"2026-09-09","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"SUSE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can bypass repository signature checks and credential validation in SUSE's libzypp and zypper package managers.","url":"https://insights.sbomify.com/SUSE-SU-2026-4112-1/"}