CVE-2026-32854

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 5.3%, top 8% of all CVEs by exploit prediction. 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 5%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
5%
EPSS %ILE
92%
KEV
Not listed

Published

March 24, 2026

Last Modified

July 14, 2026

Advisory Details (3)

Auto-updated Jul 15, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic

LibVNCServer httpd proxy NULL Pointer Dereference | Advisories | VulnCheck

https://www.vulncheck.com/advisories/libvncserver-httpd-proxy-null-pointer-dereference
github Patch Available🟡 PoC Available

NULL 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-5x4x
github_commit

commit dc78dee51a7e (LibVNC/libvncserver)

Fix landed in LibVNC/libvncserver commit dc78dee51a7e — awaiting tagged release

https://github.com/LibVNC/libvncserver/commit/dc78dee51a7e270e537a541a17befdf2073f5314

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libvncserver0.9.13+dfsg-2 ... 0.9.15+dfsg-6 (12 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libvncserver0.9.14+dfsg-10.9.14+dfsg-1+deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libvncserver0.9.15+dfsg-10.9.15+dfsg-1+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libvncserver0.9.15+dfsg-1, 0.9.15+dfsg-20.9.15+dfsg-3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 27× 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.

Showing the most recent 100 of 103 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 15:08 UTCOSV refresh
  15. 2026-09-02 14:11 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-09-01 04:39 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-24 14:17 UTCEPSS rescore
Show 75 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-16 14:56 UTCEPSS rescore
  9. 2026-08-16 10:34 UTCEG score recompute
  10. 2026-08-16 10:34 UTCVendor advisory
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 19:48 UTCVendor advisory
  14. 2026-08-14 06:50 UTCEG score recompute
  15. 2026-08-14 06:50 UTCVendor advisory
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-12 21:30 UTCEG score recompute
  18. 2026-08-12 21:30 UTCVendor advisory
  19. 2026-08-12 13:50 UTCEPSS rescore
  20. 2026-08-11 21:07 UTCEG score recompute
  21. 2026-08-11 21:07 UTCVendor advisory
  22. 2026-08-11 04:09 UTCEG score recompute
  23. 2026-08-11 04:09 UTCVendor advisory
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-10 08:22 UTCVendor advisory
  26. 2026-08-09 19:24 UTCEG score recompute
  27. 2026-08-09 19:24 UTCVendor advisory
  28. 2026-08-09 13:46 UTCEPSS rescore
  29. 2026-08-09 06:26 UTCEG score recompute
  30. 2026-08-09 06:26 UTCVendor advisory
  31. 2026-08-08 16:37 UTCEPSS rescore
  32. 2026-08-08 05:44 UTCVendor advisory
  33. 2026-08-07 16:46 UTCEG score recompute
  34. 2026-08-07 16:46 UTCVendor advisory
  35. 2026-08-06 19:04 UTCEG score recompute
  36. 2026-08-06 19:04 UTCVendor advisory
  37. 2026-08-06 13:46 UTCEPSS rescore
  38. 2026-08-06 01:11 UTCEG score recompute
  39. 2026-08-06 01:11 UTCVendor advisory
  40. 2026-08-05 19:17 UTCEPSS rescore
  41. 2026-08-04 15:10 UTCEPSS rescore
  42. 2026-08-04 10:38 UTCEPSS rescore
  43. 2026-08-03 23:55 UTCEG score recompute
  44. 2026-08-03 23:55 UTCVendor advisory
  45. 2026-08-03 10:36 UTCEPSS rescore
  46. 2026-08-02 15:44 UTCEG score recompute
  47. 2026-08-02 15:44 UTCVendor advisory
  48. 2026-08-02 02:27 UTCEPSS rescore
  49. 2026-08-01 12:06 UTCOSV refresh
  50. 2026-08-01 04:16 UTCEPSS rescore
  51. 2026-07-30 16:28 UTCEPSS rescore
  52. 2026-07-30 01:30 UTCEPSS rescore
  53. 2026-07-25 14:18 UTCEPSS rescore
  54. 2026-07-25 14:18 UTCEPSS rescore
  55. 2026-07-24 14:17 UTCEPSS rescore
  56. 2026-07-24 14:17 UTCEPSS rescore
  57. 2026-07-23 14:18 UTCEPSS rescore
  58. 2026-07-23 14:18 UTCEPSS rescore
  59. 2026-07-23 03:09 UTCEG score recompute▲ 1.20
  60. 2026-07-22 14:08 UTCEPSS rescore
  61. 2026-07-21 15:24 UTCEPSS rescore
  62. 2026-07-21 15:24 UTCEPSS rescore
  63. 2026-07-20 17:08 UTCEPSS rescore
  64. 2026-07-20 17:08 UTCEPSS rescore
  65. 2026-07-19 14:31 UTCEPSS rescore
  66. 2026-07-19 14:31 UTCEPSS rescore
  67. 2026-07-19 02:29 UTCEPSS rescore
  68. 2026-07-18 10:04 UTCEPSS rescore
  69. 2026-07-18 10:04 UTCEPSS rescore
  70. 2026-07-16 17:03 UTCEPSS rescore
  71. 2026-07-16 17:03 UTCEPSS rescore
  72. 2026-07-15 16:57 UTCEPSS rescore
  73. 2026-07-15 16:57 UTCEPSS rescore
  74. 2026-07-15 02:00 UTCEPSS rescore
  75. 2026-07-15 02:00 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-32854?
CVE-2026-32854 is a high vulnerability published on March 24, 2026. 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…
When was CVE-2026-32854 disclosed?
CVE-2026-32854 was first published in the National Vulnerability Database on March 24, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32854 actively exploited?
CVE-2026-32854 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5% probability of exploitation in the next 30 days, which ranks it in the top 7.8% of all scored CVEs.
What is the CVSS score of CVE-2026-32854?
CVE-2026-32854 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-32854?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32854, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32854

Explore →

Is Your Infrastructure Affected by CVE-2026-32854?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs