CVE-2026-7828: Integer Overflow or Wraparound in uvnc UltraVNC
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.
AI Analysis
Technical Summary
CVE-2026-7828 describes an integer overflow in UltraVNC repeater (up to version 1.8.2.2) in the HTTP request logging path. The win_log() function allocates memory using malloc(sizeof(struct LIST) + strlen(line)), where line is derived from the HTTP request URI. If strlen(line) is large enough, the addition overflows, causing malloc to allocate less memory than needed. This leads to a heap buffer overflow when strcpy copies the full string into the undersized buffer. The overflow is bounded by the HTTP receive buffer size (153600 bytes), limiting exploitability to a partial heap write. The vulnerability can be triggered remotely without authentication by sending a maximally-sized URI to the repeater HTTP port.
Potential Impact
The vulnerability allows a remote unauthenticated attacker to cause a heap buffer overflow via a specially crafted HTTP request URI. The overflow is limited in size by the HTTP receive buffer, which restricts the impact to a partial heap write. There is no direct confidentiality or integrity impact reported, but availability impact is rated as low (denial of service or crash). No known exploits are reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or workaround is currently documented. Until a patch is available, restricting access to the repeater HTTP port or filtering unusually large HTTP request URIs may reduce exposure.
CVE-2026-7828: Integer Overflow or Wraparound in uvnc UltraVNC
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.
CVSS v3.1
Score 5.3medium
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-7828 describes an integer overflow in UltraVNC repeater (up to version 1.8.2.2) in the HTTP request logging path. The win_log() function allocates memory using malloc(sizeof(struct LIST) + strlen(line)), where line is derived from the HTTP request URI. If strlen(line) is large enough, the addition overflows, causing malloc to allocate less memory than needed. This leads to a heap buffer overflow when strcpy copies the full string into the undersized buffer. The overflow is bounded by the HTTP receive buffer size (153600 bytes), limiting exploitability to a partial heap write. The vulnerability can be triggered remotely without authentication by sending a maximally-sized URI to the repeater HTTP port.
Potential Impact
The vulnerability allows a remote unauthenticated attacker to cause a heap buffer overflow via a specially crafted HTTP request URI. The overflow is limited in size by the HTTP receive buffer, which restricts the impact to a partial heap write. There is no direct confidentiality or integrity impact reported, but availability impact is rated as low (denial of service or crash). No known exploits are reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or workaround is currently documented. Until a patch is available, restricting access to the repeater HTTP port or filtering unusually large HTTP request URIs may reduce exposure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- securin
- Date Reserved
- 2026-05-05T03:40:50.298Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a44a07a27e9c79719fbd732
Added to database: 07/01/2026, 05:07:06 UTC
Last enriched: 07/01/2026, 05:22:21 UTC
Last updated: 07/01/2026, 21:35:55 UTC
Views: 10
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.