News for hackers. Stuff that matters.
Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938) by deathanatos on Tuesday November 17, 2026 @06:42PM (#50539842)
> Is "the most common class of vulnerability" not supposed to be measured by a simple count?

Trivially yes? It'd be a rate of some ilk at least. Upthread, to their credit, was a "score" of undefined nature.

But also, more upthread is talking about "memory corruption", which is going to include far more than just CWE-787. CWEs are a bit weird, and things I'd include in a loose colloquail definition like that would include stack based overflows, heap based overflows (which are for some reason different in CWE land), "classic buffer overflows" (CWE-120, again, their wording), out of bounds writes, OoB reads, null derefs, and use-after-free. All separate CWEs.

Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938) by tptacek on Tuesday November 17, 2026 @06:46PM (#50539885)
It's just a category error comparison. SQLI is a web pest vulnerability; memory corruption RCE is a vulnerability research vulnerability. They're different disciplines. Web SQLI vulnerabilities are usually application-code-specific (not just "application specific", but with a specific origin in a mistake made in application code). Big ticket vulnerability research publications are generally platform vulnerabilities; one specific coding mistake impacting thousands or millions of installs.

It's very weird to look at a memory corruption RCE and say SQLI is "more common". On typical web targets, memory corruption RCE is basically unheard of (and SQLI is not the most common sev:hi vulnerability; SSRF probably outranks it).

These are just vulnerability researchers talking like vulnerability researchers.