← Back to the briefing

The agent found a TODO. There goes the afternoon.

5 stories3 min read4:03 listen

Google measures coding-agent detours, while SonicWall’s SAML bypass lands in KEV.

Listen to this edition.

Narrated using an AI voice.

Read the transcript

Hello, and welcome to It's probably nothing. A code comment doesn’t need to be malicious to send an agent off-task. Google has put some numbers on that.

Google’s internal study found agents acted on bug references in six per cent of encounters with inline TODO or FIXME references. Eighty-three per cent of those follow-up sessions were unprompted. Among detours into still-open bugs, 39 per cent involved editing code outside the requested task.

After controlling for listed developer and task characteristics, Google associated unprompted detours with 77 per cent more tokens and 105 per cent more waiting time. Still, ordinary repository clutter appears quite capable of generating its own scope creep.

Next, SonicWall’s SAML boundary has an alternative entrance. CISA added a SonicOS vulnerability to its Known Exploited Vulnerabilities catalogue on 6 November, confirming active exploitation. SonicWall’s record says valid credentials for an alternative authentication method may bypass SAML controls, potentially including SAML-enforced MFA.

This isn’t passwordless access to every firewall. SecurityWeek reports that SAML login must be enabled on the SSL VPN service. It also reports fixes in the SonicOS 7 and 8 release lines, with no workaround. SonicWall’s quoted wording is more cautious, referring to potential exploitation. Neither it nor CISA supplies attack dates, actors or victims.

An earlier development worth catching up on: OpenSSH released a fix on 5 November for a password-authentication bypass on musl Linux systems without PAM.

Alpine documents the peculiar collision. A password between 257 and 1,024 bytes makes musl’s crypt function return an asterisk, matching a target account’s stored asterisk field. Exploitation requires password authentication to be enabled, and another local account supplying a hash with a dollar-five-dollar or dollar-six-dollar prefix.

Alpine says some official tiny-cloud images can become exploitable after a qualifying hash is added. That allows login as alpine, then root elevation through passwordless doas. PAM-enabled systems, systems with password authentication disabled, and containers without sshd fall outside its affected configurations.

Alpine provides fixed packages and says sshd must be restarted. Its interim mitigation is to disable password authentication and restart the service.

Also catching up: Crédit Mutuel Arkéa disclosed on 4 November that attackers used an unnamed supplier’s platform to transfer money from the bank’s own account to other banks.

Asked about 118 million euros, the bank confirmed only the order of magnitude. Some funds were blocked, and it said a final amount was premature. Customer assets were unaffected, according to the bank, although precautionary suspensions delayed transfers. That reassurance concerns assets, not a completed assessment of customer-data exposure.

Finally, ABC reports that Who Gives A Crap disclosed exposure at a US-based marketing software supplier. The company says names, contact details, mailing addresses and total spend were involved, but not payment details, order details or passwords. Customer accounts weren’t directly accessed.

It doesn’t know whether information was copied or downloaded, and reports no evidence of misuse so far. Total spend is a useful reminder that a marketing dataset can reveal more than where to send the next email.

That’s it for this edition. Thanks for listening, and I’ll leave the agent to its TODO list.

Don't forget, all our threat intelligence comes from Mallory dot A I and open sources. If you want intelligence your team can act on, reach out for a chat.

The takeaway

A code comment doesn’t need to be malicious to send an agent off-task. Google has put some numbers on that.

01

Your TODO list is now the agent’s side quest

Google’s internal study found agents acted on bug references in 6% of encounters with inline TODO or FIXME references; 83% of those follow-up sessions were unprompted. Among detours into still-open bugs, 39% involved editing code outside the requested task.

After controlling for listed developer and task characteristics, Google associated unprompted detours with 77% more tokens and 105% more waiting time. This is observational research, not a causal experiment or a demonstrated attack. Still, ordinary repository clutter appears quite capable of generating its own scope creep.

Sources 1
02

SonicWall’s SAML boundary has an alternative entrance

CISA added CVE-2026-19868 to KEV on 6 November, confirming active exploitation. SonicWall’s CVE record says valid credentials for an alternative authentication method may bypass SAML controls, potentially including SAML-enforced MFA. This isn’t passwordless access to every firewall: SecurityWeek reports that SAML login must be enabled on the SSL VPN service.

SonicWall’s quoted wording is more cautious, referring to potential exploitation; neither it nor CISA supplies attack dates, actors or victims.

Worth asking

For affected deployments, SecurityWeek reports fixes in SonicOS 7.3.4-7013 and 8.2.3-8015, with no workaround.

Sources 5
03

An error value that passes the password check

An earlier development worth catching up on: OpenSSH released 10.6p2 on 5 November for a password-authentication bypass on musl Linux systems without PAM.

Alpine documents the peculiar collision: a 257–1024-byte password makes musl crypt() return '*', matching a target account’s stored '*' field. Exploitation requires password authentication enabled and another local account supplying a $5$ or $6$ hash.

Alpine says some official tiny-cloud images can become exploitable after a qualifying hash is added, allowing login as alpine and root elevation through passwordless doas. PAM-enabled systems, PasswordAuthentication no and containers without sshd fall outside its affected configurations.

Worth asking

Alpine provides fixed packages and says sshd must be restarted; disabling password authentication and restarting is its interim mitigation.

Sources 4
04

Arkéa’s own account, not its customers’

Also catching up: Crédit Mutuel Arkéa disclosed on 4 November that attackers used an unnamed supplier’s platform to make transfers from the bank’s own account to other banks.

Asked about €118 million, the bank confirmed only the order of magnitude: some funds were blocked, and a final amount was premature. It says customer assets were unaffected, although precautionary suspensions delayed transfers. That reassurance concerns assets, not a completed assessment of customer-data exposure.

Sources 4
05

Marketing data is still customer data

ABC reports Who Gives A Crap disclosed exposure at a US-based marketing software supplier. The company says names, contact details, mailing addresses and total spend were involved, but not payment details, order details or passwords; customer accounts weren’t directly accessed.

It doesn’t know whether information was copied or downloaded and reports no evidence of misuse so far. Total spend is a useful reminder that a marketing dataset can reveal more than where to send the next email.

Sources 2

See you tomorrow.

Read online, listen in your podcast app, or get the daily email.

Choose how to follow IPN →