we_are_coded.by CODE · The world, decoded
БГ

Concept

Vulnerabilities

What a vulnerability is, why each one gets a number, and why the patch never installs itself.

Updated on 20 November 2026 · Checked on 20 November 2026

A vulnerability is a hole in software that someone else found before you did. It is not a lapse in your judgment and not bad luck. It sits in the code until someone plugs it or someone uses it.

Every hole that goes through the official channel gets a number. CVE-2026-123007, CVE-2026-123633 - those are not product names, they are registration numbers. A number means the maker has confirmed the hole and named the affected versions. Without it you know neither what is broken nor what to update.

The hole does not ask whether you are ready. It stays open until someone closes it.

Here is what it looks like in practice. On November 18, 2026, F5 and nginx.org disclosed ten vulnerabilities in nginx. Five of them, published as nginx2root, are memory flaws: an unauthenticated attacker can crash a server worker and, per Xint's research, run commands on it. The worst one needs only HTTP/2 to be on, and it is commonly on in TLS setups. The fix is nginx 1.30.7 or 1.31.9 and a restart.

The patch does not install itself. That is the whole job. The hole is announced in public, together with the version that fixes it, and from that moment everyone knows both where the hole is and who has not plugged it yet. So you update while nobody has gone through it yet.

There is a second shift, and the numbers show it. Per Cloudflare's data, in the 2026 U.S. election cycle, break-in attempts through vulnerabilities against government election sites were 180 times more common than DDoS attacks. A site that goes down is visible right away. A break-in that gets through is not visible for months.

The visual is generated code-art, no third-party images.