Topic: patch-management
-
Linux kernel KEV remediation: verify each CVE against the distribution package and running kernel
Track five exploited kernel flaws separately. Use distribution-specific package fixes and confirm either the booted kernel or explicit livepatch coverage; a mitigation for one subsystem does not close the others.
-
Prioritising October 2026 Patch Tuesday by exploitation evidence and affected assets
A proposed patch-triage protocol turns a large release into an asset-level queue. Confirmed exploitation, exposure and business consequences guide urgency; EPSS assists where exploitation evidence is absent.
-
Confirming a security patch actually landed: matching installed versions against vendor advisories across OS families
An update job reporting success is not proof a specific vulnerability is fixed; matching the installed package or build version against the vendor's own advisory — Ubuntu USN, a RHEL-family advisory (RHSA on RHEL) via dnf updateinfo --security, Debian DSA via debsecan, Windows Get-HotFix, or a macOS build number against Apple's own security-release page — is what closes the loop, and a pending restart can leave the old, vulnerable binary still running even after that check passes.
-
Windows Shell CVE-2026-96951: verify the Windows 11 fix and preserve attachment protection
Verify the cumulative update for the exact Windows 11 release, complete the restart, and retain attachment-origin and SmartScreen controls. A missing warning is not evidence that a downloaded file is safe.
-
Chrome CVE-2026-87491: close the gap between an installed update and a relaunched browser
Google confirms exploitation of CVE-2026-87491. Managed fleets must verify both update delivery and browser relaunch, using the platform-specific release numbers and effective enterprise policies.
-
Plex Media Server October 2026 KEV response: update, review exposure and recover compromised hosts
Four exploited Plex Media Server flaws require a verified server update and a separate compromise assessment. Review remote-access mappings, published indicators and account sessions; rebuild when server integrity cannot be established.
-
Zammad and Atlassian October 2026 KEV response: select fixes by release and installation method
Zammad has a supported upgrade and an emergency old-series fix with a repository migration requirement. Its package-specific privilege flaw needs separate verification. Atlassian supplies a product-by-product fixed-version matrix.
Machine-readable: JSON