CVE-2026-44040 (GCVE-0-2026-44040)
Vulnerability from cvelistv5 – Published: 2026-07-01 03:33 – Updated: 2026-07-09 04:36- CWE-338 - Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
| URL | Tags |
|---|---|
| https://uvnc.com/ | vendor-advisory |
| https://github.com/ultravnc/UltraVNC | product |
| https://www.securin.io/zero-days/cve-2026-44040-l… |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-44040",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-07-01T12:44:56.012420Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-07-01T12:45:04.706Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"modules": [
"winvnc",
"vncviewer"
],
"product": "UltraVNC",
"vendor": "uvnc",
"versions": [
{
"lessThanOrEqual": "1.8.2.2",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Arjun Basnet, Securin (arjun.basnet@securin.io)"
}
],
"descriptions": [
{
"lang": "en",
"value": "UltraVNC through 1.8.2.2 uses a cryptographically weak pseudo-random number generator to produce VNC authentication challenge bytes. In rfb/vncauth.c:119-129, the vncRandomBytes() function seeds libc rand() with time(0) + getpid() + rand() and generates a 16-byte challenge. The combined seed space is approximately 31 bits (libc rand() internal state) and is entirely determined by publicly-observable values (wall-clock time and process ID). An attacker who can observe the authentication exchange can enumerate the seed space and predict the challenge within seconds, enabling forgery or offline brute-forcing of responses. Note: on Windows, the active code path may use vncEncryptBytes2.cpp which calls CryptGenRandom; reachability on shipped Windows binaries requires compile-graph verification and is under investigation."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.8,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-338",
"description": "Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-07-09T04:36:05.643Z",
"orgId": "33c584b5-0579-4c06-b2a0-8d8329fcab9c",
"shortName": "securin"
},
"references": [
{
"name": "UltraVNC project page",
"tags": [
"vendor-advisory"
],
"url": "https://uvnc.com/"
},
{
"name": "UltraVNC source repository",
"tags": [
"product"
],
"url": "https://github.com/ultravnc/UltraVNC"
},
{
"url": "https://www.securin.io/zero-days/cve-2026-44040-libc-rand-weak-rng-vnc-auth-challenge-ultravnc"
}
],
"source": {
"advisory": "Securin Security Advisory \u2014 FINDING-001",
"discovery": "EXTERNAL"
},
"timeline": [
{
"lang": "en",
"time": "2026-06-02T00:00:00.000Z",
"value": "Vulnerability discovered during security audit"
},
{
"lang": "en",
"time": "2026-06-17T00:00:00.000Z",
"value": "Reported to vendor (coordinated disclosure)"
},
{
"lang": "en",
"time": "2026-09-15T00:00:00.000Z",
"value": "Planned public disclosure (90-day window)"
}
],
"title": "UltraVNC vncauth.c uses time-seeded libc rand() to generate VNC authentication challenge bytes"
}
},
"cveMetadata": {
"assignerOrgId": "33c584b5-0579-4c06-b2a0-8d8329fcab9c",
"assignerShortName": "securin",
"cveId": "CVE-2026-44040",
"datePublished": "2026-07-01T03:33:20.355Z",
"dateReserved": "2026-05-05T03:40:37.003Z",
"dateUpdated": "2026-07-09T04:36:05.643Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-44040",
"date": "2026-11-17",
"epss": "0.00397",
"percentile": "0.34461"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"modules": [
"winvnc",
"vncviewer"
],
"product": "UltraVNC",
"vendor": "uvnc",
"versions": [
{
"lessThanOrEqual": "1.8.2.2",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"source": "33c584b5-0579-4c06-b2a0-8d8329fcab9c"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:uvnc:ultravnc:*:*:*:*:*:*:*:*",
"matchCriteriaId": "593F7EC1-0922-4652-817A-7D57A0F1210D",
"versionEndIncluding": "1.8.2.2",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "UltraVNC through 1.8.2.2 uses a cryptographically weak pseudo-random number generator to produce VNC authentication challenge bytes. In rfb/vncauth.c:119-129, the vncRandomBytes() function seeds libc rand() with time(0) + getpid() + rand() and generates a 16-byte challenge. The combined seed space is approximately 31 bits (libc rand() internal state) and is entirely determined by publicly-observable values (wall-clock time and process ID). An attacker who can observe the authentication exchange can enumerate the seed space and predict the challenge within seconds, enabling forgery or offline brute-forcing of responses. Note: on Windows, the active code path may use vncEncryptBytes2.cpp which calls CryptGenRandom; reachability on shipped Windows binaries requires compile-graph verification and is under investigation."
},
{
"lang": "es",
"value": "UltraVNC hasta la versi\u00f3n 1.8.2.2 utiliza un generador de n\u00fameros pseudoaleatorios criptogr\u00e1ficamente d\u00e9bil para producir bytes de desaf\u00edo de autenticaci\u00f3n VNC. En rfb/vncauth.c:119-129, la funci\u00f3n vncRandomBytes() inicializa libc rand() con time(0) + getpid() + rand() y genera un desaf\u00edo de 16 bytes. El espacio de semillas combinado es de aproximadamente 31 bits (estado interno de libc rand()) y est\u00e1 completamente determinado por valores p\u00fablicamente observables (tiempo de reloj de pared y ID de proceso). Un atacante que puede observar el intercambio de autenticaci\u00f3n puede enumerar el espacio de semillas y predecir el desaf\u00edo en segundos, lo que permite la falsificaci\u00f3n o el ataque de fuerza bruta sin conexi\u00f3n de las respuestas. Nota: en Windows, la ruta de c\u00f3digo activa puede usar vncEncryptBytes2.cpp que llama a CryptGenRandom; la accesibilidad en los binarios de Windows distribuidos requiere verificaci\u00f3n del grafo de compilaci\u00f3n y est\u00e1 bajo investigaci\u00f3n."
}
],
"id": "CVE-2026-44040",
"lastModified": "2026-10-25T17:10:00.197",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.8,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.2,
"impactScore": 2.5,
"source": "33c584b5-0579-4c06-b2a0-8d8329fcab9c",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 2.5,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-44040",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-07-01T12:44:56.012420Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-07-01T05:16:20.897",
"references": [
{
"source": "33c584b5-0579-4c06-b2a0-8d8329fcab9c",
"tags": [
"Product"
],
"url": "https://github.com/ultravnc/UltraVNC"
},
{
"source": "33c584b5-0579-4c06-b2a0-8d8329fcab9c",
"tags": [
"Product",
"Release Notes"
],
"url": "https://uvnc.com/"
},
{
"source": "33c584b5-0579-4c06-b2a0-8d8329fcab9c",
"url": "https://www.securin.io/zero-days/cve-2026-44040-libc-rand-weak-rng-vnc-auth-challenge-ultravnc"
}
],
"sourceIdentifier": "33c584b5-0579-4c06-b2a0-8d8329fcab9c",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-338"
}
],
"source": "33c584b5-0579-4c06-b2a0-8d8329fcab9c",
"type": "Secondary"
}
]
}
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-44040",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-07-01T12:44:56.012420Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-07-01T12:45:00.742Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"modules": [
"winvnc",
"vncviewer"
],
"product": "UltraVNC",
"vendor": "uvnc",
"versions": [
{
"lessThanOrEqual": "1.8.2.2",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Arjun Basnet, Securin (arjun.basnet@securin.io)"
}
],
"descriptions": [
{
"lang": "en",
"value": "UltraVNC through 1.8.2.2 uses a cryptographically weak pseudo-random number generator to produce VNC authentication challenge bytes. In rfb/vncauth.c:119-129, the vncRandomBytes() function seeds libc rand() with time(0) + getpid() + rand() and generates a 16-byte challenge. The combined seed space is approximately 31 bits (libc rand() internal state) and is entirely determined by publicly-observable values (wall-clock time and process ID). An attacker who can observe the authentication exchange can enumerate the seed space and predict the challenge within seconds, enabling forgery or offline brute-forcing of responses. Note: on Windows, the active code path may use vncEncryptBytes2.cpp which calls CryptGenRandom; reachability on shipped Windows binaries requires compile-graph verification and is under investigation."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.8,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-338",
"description": "Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-07-09T04:36:05.643Z",
"orgId": "33c584b5-0579-4c06-b2a0-8d8329fcab9c",
"shortName": "securin"
},
"references": [
{
"name": "UltraVNC project page",
"tags": [
"vendor-advisory"
],
"url": "https://uvnc.com/"
},
{
"name": "UltraVNC source repository",
"tags": [
"product"
],
"url": "https://github.com/ultravnc/UltraVNC"
},
{
"url": "https://www.securin.io/zero-days/cve-2026-44040-libc-rand-weak-rng-vnc-auth-challenge-ultravnc"
}
],
"source": {
"advisory": "Securin Security Advisory \u2014 FINDING-001",
"discovery": "EXTERNAL"
},
"timeline": [
{
"lang": "en",
"time": "2026-06-02T00:00:00.000Z",
"value": "Vulnerability discovered during security audit"
},
{
"lang": "en",
"time": "2026-06-17T00:00:00.000Z",
"value": "Reported to vendor (coordinated disclosure)"
},
{
"lang": "en",
"time": "2026-09-15T00:00:00.000Z",
"value": "Planned public disclosure (90-day window)"
}
],
"title": "UltraVNC vncauth.c uses time-seeded libc rand() to generate VNC authentication challenge bytes"
}
},
"cveMetadata": {
"assignerOrgId": "33c584b5-0579-4c06-b2a0-8d8329fcab9c",
"assignerShortName": "securin",
"cveId": "CVE-2026-44040",
"datePublished": "2026-07-01T03:33:20.355Z",
"dateReserved": "2026-05-05T03:40:37.003Z",
"dateUpdated": "2026-07-09T04:36:05.643Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.