CVE-2026-7839: Use of Hard-coded Credentials in uvnc UltraVNC
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.
AI Analysis
Technical Summary
UltraVNC repeater up to version 1.8.2.2 initializes its HTTP administration server with a hardcoded default password "adminadmi2" if the settings file settings2.txt is missing on first run. The authentication mechanism uses HTTP Basic-auth without rate limiting or lockout, allowing any remote attacker who can access the repeater's HTTP port (default TCP 80) to authenticate as administrator. This grants full control over repeater configuration, including allow/deny rules and session visibility. No vendor advisory or patch information is provided, and the vulnerability is publicly documented with a CVSS 3.1 score of 9.1 (critical).
Potential Impact
An unauthenticated remote attacker can gain administrative access to the UltraVNC repeater by using the hardcoded default password. This access allows the attacker to modify repeater configuration, control allow/deny rules, and view session information. The vulnerability does not affect availability but compromises confidentiality and integrity at a high level.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should restrict network access to the repeater's HTTP administration port (default TCP 80) to trusted hosts only and ensure the settings2.txt file is properly configured to avoid default password usage.
CVE-2026-7839: Use of Hard-coded Credentials in uvnc UltraVNC
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.
CVSS v3.1
Score 9.1critical
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
UltraVNC repeater up to version 1.8.2.2 initializes its HTTP administration server with a hardcoded default password "adminadmi2" if the settings file settings2.txt is missing on first run. The authentication mechanism uses HTTP Basic-auth without rate limiting or lockout, allowing any remote attacker who can access the repeater's HTTP port (default TCP 80) to authenticate as administrator. This grants full control over repeater configuration, including allow/deny rules and session visibility. No vendor advisory or patch information is provided, and the vulnerability is publicly documented with a CVSS 3.1 score of 9.1 (critical).
Potential Impact
An unauthenticated remote attacker can gain administrative access to the UltraVNC repeater by using the hardcoded default password. This access allows the attacker to modify repeater configuration, control allow/deny rules, and view session information. The vulnerability does not affect availability but compromises confidentiality and integrity at a high level.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should restrict network access to the repeater's HTTP administration port (default TCP 80) to trusted hosts only and ensure the settings2.txt file is properly configured to avoid default password usage.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- securin
- Date Reserved
- 2026-05-05T07:30:58.064Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a44a07b27e9c79719fbd787
Added to database: 07/01/2026, 05:07:07 UTC
Last enriched: 07/08/2026, 13:02:35 UTC
Last updated: 08/14/2026, 12:41:12 UTC
Views: 125
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.