The attack server came with a résumé
CrowdStrike found exposed AI-tool records tied to the South Korean bank campaign, including a résumé request. The operator’s identity remains unconfirmed.
Read the pick: The attack server came with a résuméX OPPORTUNITY RADAR / DISPATCH
GitLab’s AI gateway joins the Friday patch queue
A CVSS 9.9 flaw puts affected self-hosted AI Gateways on the urgent patch list. The sandbox would like a word with whoever gave it the keys, droog.
2 min readSources
Friday’s maintenance memo has arrived, droogies. GitLab’s AI Gateway needs attention, and the critical score is 9.9. The future of software has kept one beloved tradition: an urgent patch just as you were thinking about logging off.[1]
Memo one: the sandbox has an exit
CVE-2026-90970, published on October 2, concerns custom-flow prompt templates. GitLab says an authenticated user with Duo Agent Platform access could, under certain conditions, use a crafted flow configuration to escape the template sandbox and execute arbitrary commands on the gateway. The advisory leaves those conditions unspecified.[1][2]
That is a serious boundary failure. Keep the access requirement attached to the headline; it matters.
Memo two: check the actual gateway
GitLab urges affected self-hosted gateway operators to update immediately. Its published version ranges and first fixed releases are:[1]
- AI Gateway 18.1.6 up to, but excluding, 19.2.4: fixed in 19.2.4
- AI Gateway 19.3 up to, but excluding, 19.3.2: fixed in 19.3.2
- AI Gateway 19.4 up to, but excluding, 19.4.1: fixed in 19.4.1[1]
These numbers belong to the AI Gateway. GitLab documents a separately deployed gateway image and tells operators to match its release to their GitLab minor version. Follow GitLab’s gateway upgrade guidance and verify the running version. The advisory lists no fixed release below 19.2.4. A reassuring entry in the change calendar cannot do that job for you.[1][3]
GitLab-hosted gateways are already patched. GitLab says customers on GitLab.com, GitLab Dedicated, or self-managed GitLab using its hosted gateway need no action for this flaw. Self-hosted comes with its own little patch queue. How very bespoke.[1]
Memo three: leave the invented breach out
GitLab’s advisory does not say whether the flaw has been exploited. CISA’s October 2 assessment, recorded in the official CVE file, marks exploitation as “none.” That is a dated assessment, not a promise about every installation.[1][2]
Viddy the running version, the deployment boundary and the person responsible for fixing it. Give the AI gateway the same dull scrutiny as the rest of production. Boring is horrorshow when the alternative is somebody else choosing the commands.
FOLLOW THE SOURCES.
Checked Oct 2, 2026. Numbered references point to the evidence behind factual passages. Commentary is our own.
- GitLab AI Gateway critical patch release: 19.2.4, 19.3.2 and 19.4.1 (opens in a new tab)GitLabBack to cited passage
- CVE-2026-90970: official CVE record and CISA assessment (opens in a new tab)CVE Program / GitLab / CISABack to cited passage
- Install and upgrade the GitLab AI Gateway (opens in a new tab)GitLab DocsBack to cited passage
KEEP YOUR GLAZZIES OPEN
READ NEXT.
Epic’s AI security lesson comes with a patch queue
Epic’s security push deserves attention. So does the gap between a six-week headline and what the company says is still moving, droogies.
Read the pick: Epic’s AI security lesson comes with a patch queue