Skip to content

Topic

Web Framework Security

Critical vulnerabilities and patch cycles in application frameworks such as Next.js.

Current stories

securityOne report1 publisher

Next.js 16.4.1 and 15.5.28 fix two 9.5-rated code-execution flaws in caching and SVG rendering

Next.js released versions 16.4.1 and 15.5.28 on October 14 to fix two unauthenticated code-execution flaws that Vercel rated CVSS 9.5. As of October 15 the caching flaw had no CVE and no workaround, so npm audit may stay quiet and only the upgrade closes it.

Reality

Evidence55
Adoption
Not scored
Hype gap+10
Incentives
Not scored
Confidence55
buildOne report1 publisher

Django 6.1 cuts hardened password hashes down to its new 1.5M-iteration default at login

Django 6.1 raised its default PBKDF2 iteration count from 1.2M to 1.5M, adding about 50 to 90ms of CPU per login in a dev.to benchmark. The same tests show each stored hash rewritten on its owner's next login, including hashes deliberately set stronger than the new default.

Publishers:dev.to

Reality

Evidence58
Adoption
Not scored
Hype gap+20
Incentives
Not scored
Confidence55
buildOne report1 publisher

Chunked DELETE requests can smuggle a hidden second request through Next.js rewrites

Next.js's bundled http-proxy 1.18.1 stamps Content-Length: 0 on chunked DELETE and OPTIONS rewrites, so a hidden second request reaches the backend. Whether it reaches anything sensitive depends on how the next hop frames requests and which internal routes the backend opens to its proxy.

Publishers:dev.to

Reality

Evidence62
Adoption
Not scored
Hype gap+15
Incentives
Not scored
Confidence56
buildOne report1 publisher

Seven hundred client fingerprints cover React2Shell's 8,163 source addresses

GreyNoise's January tally of React2Shell traffic shows payload text mutating freely while the client tooling behind it stays nearly fixed. That decides what a perimeter rule should match on.

Publishers:greynoise.io

Reality

Evidence58
Adoption72
Hype gap+18
Incentives80
Confidence55