{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-7829 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-7829 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-7829 is a high-severity memory corruption vulnerability in uvnc UltraVNC, published on 1 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-7829 and fix it if it is affected.\n\nWhat it is: CVE-2026-7829 is a high-severity memory corruption vulnerability in uvnc UltraVNC, published on 1 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-7829 in the wild and no public exploit code.\n\nAffected product: uvnc UltraVNC. 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-7829/ (Markdown: https://insights.sbomify.com/CVE-2026-7829/index.md)","id":"CVE-2026-7829","markdown":"https://insights.sbomify.com/CVE-2026-7829/index.md","name":"CVE-2026-7829","record":{"aliases":["GHSA-fxj2-5q9g-wmp9"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"VNC repeater","requires_auth":"high_privilege","summary":"An authenticated administrator can trigger an out-of-bounds write in the rule parser to achieve code execution on the UltraVNC repeater host.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"securin","cpe":[{"product":"ultravnc","vendor":"uvnc"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"UltraVNC repeater through 1.8.2.2 contains a post-authentication out-of-bounds write in the allow/deny rule parser. In repeater/webgui/settings.c:225-272, after strncpy_s copies a rule token into temp1[rule1] (25-byte destination) or temp2/temp3 (16-byte destination), the code unconditionally writes a NUL terminator at temp1[rule1][len] = 0 without clamping len to the destination size. When an authenticated administrator saves a rule with a token length equal to or greater than the destination size, the NUL byte is written one or more bytes past the end of the stack-allocated array, corrupting adjacent stack data. An attacker who has obtained admin credentials (including via CVE-2026-7839 default password) can trigger this to gain code execution on the repeater host.","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":"UltraVNC repeater authenticated out-of-bounds write in rule parser via oversized token","id":"CVE-2026-7829","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"UltraVNC MS-Logon II uses 64-bit Diffie-Hellman and seeded libc rand() enabling credential interception","id":"CVE-2026-7830"},"packages":[],"prev":{"headline":"UltraVNC repeater integer overflow in win_log malloc leading to heap overflow","id":"CVE-2026-7828"},"products":["UltraVNC"],"published":"2026-07-01","related":[{"cvss_score":9.8,"headline":"Memory corruption in UltraVNC","id":"CVE-2019-8264","kev_date_added":null,"published":"2019-03-09"},{"cvss_score":9.8,"headline":"Memory corruption in UltraVNC","id":"CVE-2019-8265","kev_date_added":null,"published":"2019-03-09"},{"cvss_score":9.8,"headline":"Memory corruption in UltraVNC","id":"CVE-2019-8266","kev_date_added":null,"published":"2019-03-09"},{"cvss_score":9.8,"headline":"Memory corruption in UltraVNC","id":"CVE-2019-8280","kev_date_added":null,"published":"2019-03-09"},{"cvss_score":9.8,"headline":"Memory corruption in UltraVNC","id":"CVE-2018-15361","kev_date_added":null,"published":"2019-03-05"},{"cvss_score":9.8,"headline":"Integer overflow in UltraVNC","id":"CVE-2019-8260","kev_date_added":null,"published":"2019-03-05"},{"cvss_score":9.8,"headline":"Integer overflow in UltraVNC","id":"CVE-2019-8261","kev_date_added":null,"published":"2019-03-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-07-09","vendors":["uvnc"]},"summary":"An authenticated administrator can trigger an out-of-bounds write in the rule parser to achieve code execution on the UltraVNC repeater host.","url":"https://insights.sbomify.com/CVE-2026-7829/"}