Kyverno flaw rated 9.9 works with a low-privileged account
Kyverno CVE-2026-124440, CVSS 9.9 ·
In this episode
The facts
- CVE-2026-124440 is a flaw in kyverno.
- CVE-2026-124440 is classed as CWE-441 in MITRE's weakness list.
- According to its CVSS rating, CVE-2026-124440 can be exploited remotely over the network, with a low-privileged account and without user interaction. A successful attack would fully compromise the confidentiality, integrity and availability of the affected system. Its impact can reach beyond the vulnerable component.
- CVE-2026-124440 is rated 9.9 out of 10 on the CVSS severity scale.
Sources
The panel
Jordan Pike AI host
CVE-2026-124440 is a flaw in kyverno, and it's classed as CWE-441 in MITRE's weakness list.
Jordan Pike AI host
CVE-2026-124440 is rated 9.9 out of 10 on the CVSS severity scale. According to its CVSS rating, it can be exploited remotely over the network, with a low-privileged account and without user interaction. A successful attack would fully compromise the confidentiality, integrity and availability of the affected system, and its impact can reach beyond the vulnerable component.
Jordan Pike AI host
If you run kyverno, this one is yours. Dex, how would an attacker see it?
Dex Moreno AI analyst
Start with the entry fee: a low-privileged account, reached over the network, and nobody has to click anything. Any ordinary foothold becomes the way in. The CVSS note that impact can reach beyond the vulnerable component matters most. It means the attacker doesn't stay in the box they hit, and a stepping stone is exactly what they want. Flaws with network reach and a low bar tend to get weaponised quickly once details circulate. The facts we have don't report any exploitation, so this is the typical pattern and not something confirmed here.
Dex Moreno AI analyst
A low-privileged account as the only requirement. Honestly, a very welcoming attacker experience. Five stars for hospitality. The target deserved better.
Jordan Pike AI host
Please don't leave a review.
Maya Okafor AI analyst
CWE-441 is the unintended proxy or intermediary class, better known as the confused deputy. A trusted component does something on a caller's behalf without checking that the caller may ask for it. It keeps happening because code checks who you are and forgets to check whether this request is yours to make. A complete fix checks the original caller's rights on every path where the component acts for someone. Fixing one path is a partial fix. The facts don't say where the bug sits, so I won't guess, but look for sibling paths with the same trust.
Maya Okafor AI analyst
A confused deputy is the coworker who does anything if you ask politely. Great for morale, terrible for access control.
Jordan Pike AI host
So, the most popular person in the building.
Sam Kowalski AI analyst
Assume someone may have tried this before anyone wrote the CVE. Low-privileged accounts are everywhere, so the first question is how far back your logs go. Pull the logs from kyverno and from whatever it acts on, then look for requests that don't match the caller's normal rights. Your audit trail is fine, I'm sure. Right up until someone asks how long you keep it. My action: preserve those logs now, before rotation decides the answer for you.
Jordan Pike AI host
Patch now, or scope first? Dex, you look like you have a view.
Dex Moreno AI analyst
Exposure sets the order. Who can reach it from the network, and how many low-privileged accounts exist? That ranking decides what you touch first. If the fix isn't out yet, you tighten who can reach it and who holds those accounts, and you watch closely. Patching isn't the end either. Assume a foothold might already exist and go looking for it.
Maya Okafor AI analyst
I'll push back. Scoping is fine, but it isn't a substitute for the fix. Apply the update as soon as one ships, because we don't know yet from these facts whether one exists. Any restriction in the meantime is a bridge, so give it an end date. And ask whether the patch closes the whole class or just one route. My action: read the fix for root cause, not only the version number.
Rina Takahashi AI analyst
On attribution: nobody in these facts names an actor, and none reports exploitation. The 9.9 is a rating in the CVE record, not a sighting. That could change if a trusted source later reports attacks, and then the panel's view is that it becomes an emergency. My action: watch for an advisory or exploitation report, and check who says so and how confident they are.
Jordan Pike AI host
So for Monday: find where you run kyverno, rank it by who can reach it, keep the logs, and patch when the fix lands. Any stopgap gets an end date.