https://pwn.watch/t/red-hat Live security incidents worldwide: CVEs, patch status, fixed versions, advisories and the posts that broke them. en Fri, 23 Oct 2026 01:02:13 GMT https://pwn.watch/i/keycloak-cve-2026-18963-reset-credentials-takeover https://pwn.watch/i/keycloak-cve-2026-18963-reset-credentials-takeover Fri, 23 Oct 2026 01:02:13 GMT critical <p>A flaw in Keycloak's reset-credentials flow (keycloak-services) lets an unauthenticated attacker force a password reset for any user without clicking the emailed verification link, then set new credentials and take over the account. Red Hat rates it CVSS 9.1. Fixes shipped in August (26.4.15, 26.6.6, 26.7.2); on Oct 21 a full proof-of-concept with check and takeover modes was published on Exploit-DB, so unpatched Keycloak instances should be upgraded now.</p> <p><strong>Status:</strong> live · <strong>Patch:</strong> patched · <strong>Fixed in:</strong> 26.4.15, 26.6.6, 26.7.2, 26.8.0 and later</p> <p><strong>Latest updates:</strong></p><ul><li>2026-10-21: Exploit-DB publishes EDB-52699 &quot;Keycloak 26.7.2 - Unauthenticated Account Takeover&quot; by Abel Maldonado (Orevim): a PoC with a safe --check mode and a --set-password takeover mode, tested on Keycloak 26.6.2. (<a href="https://www.exploit-db.com/exploits/52699">source</a>)</li><li>2026-08-18: CVE-2026-18963 published with GitHub advisory GHSA-4gv3-mc9p-5wqc (critical); fixed in keycloak-services 26.4.15, 26.6.6 and 26.7.2, with Red Hat errata for Red Hat Build of Keycloak. (<a href="https://github.com/advisories/GHSA-4gv3-mc9p-5wqc">source</a>)</li></ul> <p><strong>CVEs:</strong> CVE-2026-18963</p> https://pwn.watch/i/red-hat-consulting-gitlab-breach-october-2025 https://pwn.watch/i/red-hat-consulting-gitlab-breach-october-2025 Fri, 10 Oct 2025 00:00:00 GMT high <p>The Crimson Collective broke into a self-managed GitLab instance used by Red Hat Consulting and claimed about 570 GB from 28,000 repos, including roughly 800 Customer Engagement Reports with infrastructure, config and credential details. Red Hat confirmed the access and said its products, supply chain and hosted services were not affected. ShinyHunters later joined the extortion.</p> <p><strong>Status:</strong> closed · <strong>Patch:</strong> no-fix-needed</p> <p><strong>Latest updates:</strong></p><ul><li>2025-10-10: FINRA alert to member firms (<a href="https://www.finra.org/rules-guidance/guidance/red-hat-security-incident-20251010">source</a>)</li><li>2025-10-02: Red Hat confirms the incident (<a href="https://www.redhat.com/en/blog/security-update-incident-related-red-hat-consulting-gitlab-instance">source</a>)</li><li>2025-10-01: Crimson Collective claims the Red Hat GitLab theft (<a href="https://www.bleepingcomputer.com/news/security/red-hat-confirms-security-incident-after-hackers-breach-gitlab-instance/">source</a>)</li></ul>