{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-7839 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-7839 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-7839 is a critical 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-7839 and fix it if it is affected.\n\nWhat it is: CVE-2026-7839 is a critical 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-7839 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-7839/ (Markdown: https://insights.sbomify.com/CVE-2026-7839/index.md)","id":"CVE-2026-7839","markdown":"https://insights.sbomify.com/CVE-2026-7839/index.md","name":"CVE-2026-7839","record":{"aliases":["GHSA-h7cc-6wq3-9h7x"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"VNC repeater","requires_auth":"none","summary":"Remote attackers can gain full administrative control of UltraVNC repeater by using a hardcoded default password on fresh installations.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"securin","cpe":[{"product":"ultravnc","vendor":"uvnc"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"UltraVNC repeater through 1.8.2.2 initializes the HTTP administration server with a hardcoded default password. In repeater/webgui/settings.c:197, when settings2.txt is absent on first run the repeater writes the literal string \"adminadmi2\" as the admin password via strcpy_s(saved_password, 64, \"adminadmi2\"). The HTTP Basic-auth handler wi_decode_auth() checks this password without rate-limiting or lockout. Any remote attacker who can reach the repeater HTTP port (default TCP 80) can authenticate as administrator using the well-known default credential on a fresh or unmodified installation, gaining full control of the repeater configuration including allow/deny rules and session visibility.","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 ships hardcoded default admin password allowing unauthenticated admin access","id":"CVE-2026-7839","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"UltraVNC repeater HTTP server global buffer overflow via long URI (pre-auth RCE)","id":"CVE-2026-7840"},"packages":[],"prev":{"headline":"UltraVNC viewer heap buffer overflow via integer overflow in RFB connection-failure reason length","id":"CVE-2026-7838"},"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":"total"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["uvnc"]},"summary":"Remote attackers can gain full administrative control of UltraVNC repeater by using a hardcoded default password on fresh installations.","url":"https://insights.sbomify.com/CVE-2026-7839/"}