Google V8 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows rem…

published 2011-12-30 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4940

cvss: 5.0; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.4%; EPSS 1.4% chance of exploitation in 30 days, percentile 73%
public exploits: 0; none known

Google V8 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters, as demonstrated by attacks against Node.js.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-5037 updated 2025-11-21 cvss 5.0

v8: hash table collisions CPU usage DoS (oCERT-2011-003)

Red Hat All currently supported Red Hat products
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.44% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness

CWE-20 Improper Input Validation

References

nruns.com /_downloads/advisory28122011.pdf
kb.cert.org /vuls/id/903934
third-party-advisory, us-government-resource
archives.neohapsis.com /archives/bugtraq/2011-12/0181.html
mailing-list
ocert.org /advisories/ocert-2011-003.html

Sources

CVE List CVE-2011-5037
NVD CVE-2011-5037

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary