{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-7828 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-7828 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-7828 is a medium-severity vulnerability in uvnc UltraVNC, published on 1 Jul 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-7828 and fix it if it is affected.\n\nWhat it is: CVE-2026-7828 is a medium-severity vulnerability in uvnc UltraVNC, published on 1 Jul 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-7828 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-7828/ (Markdown: https://insights.sbomify.com/CVE-2026-7828/index.md)","id":"CVE-2026-7828","markdown":"https://insights.sbomify.com/CVE-2026-7828/index.md","name":"CVE-2026-7828","record":{"aliases":["GHSA-hpq9-2mqh-7fg9"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"VNC repeater server","requires_auth":"none","summary":"A remote unauthenticated attacker can trigger a heap buffer overflow via integer overflow in HTTP logging, potentially causing denial of service.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"securin","cpe":[{"product":"ultravnc","vendor":"uvnc"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"UltraVNC repeater through 1.8.2.2 contains an integer overflow in the HTTP request logging path. In repeater/webgui/settings.c:336, the win_log() function allocates list nodes via malloc(sizeof(struct LIST) + strlen(line)), where line is derived from HTTP request URIs. If strlen(line) is sufficiently large, the addition overflows to a value smaller than sizeof(struct LIST), causing a heap allocation smaller than required. The subsequent strcpy of the full string into the undersized allocation produces a heap buffer overflow. In the current implementation this overflow is bounded by the HTTP receive buffer size (WI_RXBUFSIZE = 153600 bytes, well below SIZE_MAX on 32-bit builds), limiting practical exploitability to a partial heap write. A remote unauthenticated attacker can trigger the theoretical overflow path by sending a maximally-sized URI in an HTTP request to the repeater HTTP port.","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 integer overflow in win_log malloc leading to heap overflow","id":"CVE-2026-7828","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"UltraVNC repeater authenticated out-of-bounds write in rule parser via oversized token","id":"CVE-2026-7829"},"packages":[],"prev":{"headline":"Stack-based buffer overflow in FalkorDB _RdbLoadEntity via unbounded property count in crafted RDB","id":"CVE-2026-7827"},"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["uvnc"]},"summary":"A remote unauthenticated attacker can trigger a heap buffer overflow via integer overflow in HTTP logging, potentially causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-7828/"}