KEV flaws exploited across platforms; Rails patch released
KEV exploits and Rails fix ·
In this episode
- GitLab bug under attack: what's new on the fix
- Brotli flaw added to KEV, patch quickly
- CISA reports exploitation of Magento file-upload flaw
- CVE-2026-119977: WordPress Core
- CVE-2026-122006: rubyonrails Active Storage
The facts
- Attackers are exploiting CVE-2026-97229, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- Attackers are exploiting CVE-2026-111497, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- Attackers are exploiting CVE-2026-48356, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- Attackers are exploiting CVE-2026-48356, according to CISA.
- Attackers are exploiting CVE-2026-111497, according to CISA.
- Attackers are exploiting CVE-2026-111357, according to CISA.
- Attackers are exploiting Inno installers, according to Microsoft.
- Attackers are exploiting CVE-2026-119977, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- A fix is available for Ruby on Rails.
- CVE-2026-119977 is a flaw in WordPress Core.
- CVE-2026-122006 is a flaw in rubyonrails Active Storage.
Sources
The panel
Jordan Pike AI host
CISA adds CVE-2026-119977 to its Known Exploited Vulnerabilities catalog. The flaw lives in WordPress Core.
Dex Moreno AI analyst
Exploiting that WordPress Core flaw lets an attacker run code on the site, hijack the web application, and use it as a foothold for further moves. Because it’s a KEV entry, patch within 72 hours.
Sam Kowalski AI analyst
Start with the web server access logs and any WordPress-related logs. Hunt for unexpected processes or logins from unknown IPs, and isolate the host while you apply the fix.
Jordan Pike AI host
CISA flags CVE-2026-97229 and CVE-2026-111357 as actively exploited.
Dex Moreno AI analyst
A compromised component with those flaws could let an attacker steal credentials and launch jobs that reach internal services. Prioritize patching before the breach spreads.
Sam Kowalski AI analyst
Pull the audit logs, look for job-type activity from unknown sources, and verify any token usage. Quarantine any host that can’t be patched immediately.
Jordan Pike AI host
CISA reports active exploitation of CVE-2026-111497 and CVE-2026-48356.
Dex Moreno AI analyst
Those vulnerabilities can enable remote code execution on affected binaries, giving attackers a foothold on the server and a path to other systems. Deploy the vendor updates without delay.
Sam Kowalski AI analyst
Check crash reports and unexpected restarts, correlate with inbound traffic that may have triggered the flaw, and monitor after the update.
Jordan Pike AI host
CISA adds CVE-2026-48356 and CVE-2026-111497 as exploited flaws.
Dex Moreno AI analyst
A malicious file upload could give the attacker a shell on the server, opening the door to data theft and lateral movement. Patch and block untrusted uploads now.
Sam Kowalski AI analyst
Search for unexpected file-upload events in the logs and scan the webroot for new scripts. Quarantine the server and roll out the fix.
Jordan Pike AI host
Microsoft says attackers are exploiting Inno installer packages.
Dex Moreno AI analyst
Compromised installers can drop payloads during software setup, giving the attacker persistent code on any machine that runs the installer. Block unsigned installers and apply the vendor’s hardening guidance.
Sam Kowalski AI analyst
Audit event logs for installer execution events from unknown sources. Remove rogue installer binaries and enforce code-signing policies.
Dex Moreno AI analyst
Next, next, finish: the one setup wizard that really commits to the finish. The target deserved better.
Jordan Pike AI host
Click next to continue. Please don't.
Jordan Pike AI host
CVE-2026-122006 is a flaw in Ruby on Rails Active Storage, and The Hacker News reports a fix is available.
Dex Moreno AI analyst
The Active Storage flaw could allow arbitrary file writes, potentially leading to code execution. Because it isn’t a KEV entry, schedule the patch in your regular cycle but test for abuse now.
Sam Kowalski AI analyst
Watch for unusual file-handling activity in application logs and apply the vendor patch as soon as it’s released, then verify the fix with a controlled test.
Jordan Pike AI host
Patch the KEV flaws within three days, monitor for signs of compromise, and keep your update pipeline humming.