{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-59679 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-59679 is a critical memory corruption vulnerability in Container suse/kiosk/tigervnc-x11vnc:1.14-63.8, published on 10 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 CVE-2026-59679 and fix it if it is affected.\n\nWhat it is: CVE-2026-59679 is a critical memory corruption vulnerability in Container suse/kiosk/tigervnc-x11vnc:1.14-63.8, published on 10 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 CVE-2026-59679 in the wild and no public exploit code.\n\nAffected product: Container suse/kiosk/tigervnc-x11vnc:1.14-63.8. 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-59679/ (Markdown: https://insights.sbomify.com/CVE-2026-59679/index.md)","id":"CVE-2026-59679","markdown":"https://insights.sbomify.com/CVE-2026-59679/index.md","name":"CVE-2026-59679","record":{"aliases":["AZL-101730","DEBIAN-CVE-2026-59679","GHSA-g44m-wpf7-gr7x","UBUNTU-CVE-2026-59679"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"X11 font library","requires_auth":"none","summary":"A malicious font server can trigger heap out-of-bounds read and write in libXfont2, potentially leading to code execution or denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"suse","cpe":[],"cvss":{"score":9.2,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"fs_read_glyphs() in the libXfont2 font-server client (src/fc/fserve.c) indexes the per-character encoding[] array using num_chars from the FS_QueryXBitmaps16 reply, but that array was allocated with a size derived from num_extents in the separate FS_QueryXExtents16 reply. The two CARD32 fields are never cross-checked.\nA malicious or compromised font server can send a small num_extents (e.g. 1) in the extents reply, then a large num_chars (e.g. 100000) in the bitmaps reply. This causes attacker-controlled out-of-bounds heap read and writes.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"fs_read_glyphs() heap OOB read/write via encoding array index mismatch in libXfont2","id":"CVE-2026-59679","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"yast2-users: OS command injection via LDAP-supplied shadowLastChange/shadowExpire attribute","id":"CVE-2026-59680"},"packages":[],"prev":{"headline":"Missing authorization in PortProtonQt","id":"CVE-2026-59678"},"products":["Container suse/kiosk/tigervnc-x11vnc:1.14-63.8","Container suse/kiosk/xorg:21.1-83.7","Image SLES-SAP-Azure","Image SLES-SAP-Azure-3P","Image SLES-SAP-BYOS-Azure","Image SLES-SAP-BYOS-EC2","Image SLES-SAP-BYOS-GCE","Image SLES-SAP-GCE","Image SLES-SAP-GCE-3P","Image SLES-SAPCAL-GCE","Image SLES12-SP5-Azure-SAP-BYOS","Image SLES12-SP5-Azure-SAP-On-Demand","Image SLES12-SP5-EC2-SAP-BYOS","Image SLES12-SP5-EC2-SAP-On-Demand","Image SLES12-SP5-GCE-SAP-BYOS","Image SLES12-SP5-GCE-SAP-On-Demand","Image SLES15-SP6-SAP","Image SLES15-SP6-SAP-Azure","Image SLES15-SP6-SAP-Azure-3P","Image SLES15-SP6-SAP-BYOS","Image SLES15-SP6-SAP-BYOS-Azure","Image SLES15-SP6-SAP-BYOS-EC2","Image SLES15-SP6-SAP-BYOS-GCE","Image SLES15-SP6-SAP-EC2","Image SLES15-SP6-SAP-GCE","Image SLES15-SP6-SAP-Hardened","Image SLES15-SP6-SAP-Hardened-Azure","Image SLES15-SP6-SAP-Hardened-BYOS","Image SLES15-SP6-SAP-Hardened-BYOS-Azure","Image SLES15-SP6-SAP-Hardened-BYOS-EC2","Image SLES15-SP6-SAP-Hardened-BYOS-GCE","Image SLES15-SP6-SAP-Hardened-EC2","Image SLES15-SP6-SAP-Hardened-GCE","Image SLES15-SP6-SAPCAL","Image SLES15-SP6-SAPCAL-Azure","Image SLES15-SP6-SAPCAL-EC2","Image SLES15-SP6-SAPCAL-GCE","Image SLES15-SP7-SAP-Azure","Image SLES15-SP7-SAP-Azure-3P","Image SLES15-SP7-SAP-BYOS-Azure","Image SLES15-SP7-SAP-BYOS-EC2","Image SLES15-SP7-SAP-BYOS-GCE","Image SLES15-SP7-SAP-EC2","Image SLES15-SP7-SAP-GCE","Image SLES15-SP7-SAP-GCE-3P","Image SLES15-SP7-SAP-Hardened-Azure","Image SLES15-SP7-SAP-Hardened-BYOS-Azure","Image SLES15-SP7-SAP-Hardened-BYOS-EC2","Image SLES15-SP7-SAP-Hardened-BYOS-GCE","Image SLES15-SP7-SAP-Hardened-GCE","Image SLES15-SP7-SAPCAL-Azure","Image SLES15-SP7-SAPCAL-EC2","Image SLES15-SP7-SAPCAL-GCE","SUSE Liberty Linux 10","SUSE Liberty Linux 8","SUSE Liberty Linux 9","SUSE Linux Enterprise Desktop 15 SP7","SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS","SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS","SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS","SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS","SUSE Linux Enterprise Module for Basesystem 15 SP7","SUSE Linux Enterprise Server 12 SP5-LTSS","SUSE Linux Enterprise Server 15 SP4-LTSS","SUSE Linux Enterprise Server 15 SP5-LTSS","SUSE Linux Enterprise Server 15 SP6-LTSS","SUSE Linux Enterprise Server 15 SP7","SUSE Linux Enterprise Server 16.0","SUSE Linux Enterprise Server LTSS Extended Security 12 SP5","SUSE Linux Enterprise Server for SAP Applications 15 SP4","SUSE Linux Enterprise Server for SAP Applications 15 SP5","SUSE Linux Enterprise Server for SAP Applications 15 SP6","SUSE Linux Enterprise Server for SAP Applications 15 SP7","SUSE Linux Enterprise Server for SAP applications 16.0","SUSE Manager Proxy LTS 4.3","SUSE Manager Retail Branch Server LTS 4.3","SUSE Manager Server LTS 4.3","libXfont2","openSUSE Leap 16.0","openSUSE Tumbleweed"],"published":"2026-09-10","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":"total"},"state":"PUBLISHED","updated":"2026-09-10","vendors":["SUSE","libXfont2"]},"summary":"A malicious font server can trigger heap out-of-bounds read and write in libXfont2, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2026-59679/"}