LibVNCServer versions 0.9.15 and prior (fixed in commit dc78dee) contain null pointer dereference vulnerabilities in the HTTP proxy handlers within httpProcessInput() in httpd.c that allow remote attackers to cause a denial of service by sending specially crafted HTTP requests. Attackers can exploit missing validation of strchr() return values in the CONNECT and GET proxy handling paths to trigger null pointer dereferences and crash the server when httpd and proxy features are enabled.
CVE-2026-32854
This medium-severity CVE scores 6.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 6.3(low)
- EPSS
- 91.7%
- KEV
- Not listed
Published
March 24, 2026
Last Modified
July 14, 2026
Advisory Details (3)
Auto-updated Jul 15, 2026LibVNCServer httpd proxy NULL Pointer Dereference | Advisories | VulnCheck
https://www.vulncheck.com/advisories/libvncserver-httpd-proxy-null-pointer-dereferenceNULL pointer dereferences in httpd proxy handlers via malformed CONNECT/GET requests · Advisory · LibVNC/libvncserver · GitHub
https://github.com/LibVNC/libvncserver/security/advisories/GHSA-xjp8-4qqv-5x4xcommit dc78dee51a7e (LibVNC/libvncserver)
Fix landed in LibVNC/libvncserver commit dc78dee51a7e — awaiting tagged release
https://github.com/LibVNC/libvncserver/commit/dc78dee51a7e270e537a541a17befdf2073f5314Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 19:21 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
- 2026-07-14 19:01 UTCEG score recompute
- 2026-07-14 19:00 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-32854?
When was CVE-2026-32854 disclosed?
Is CVE-2026-32854 actively exploited?
What is the CVSS score of CVE-2026-32854?
How do I remediate CVE-2026-32854?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-32854
Is Your Infrastructure Affected by CVE-2026-32854?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.