Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.309 ·

Stricter rules for an organization's list of trusted gateway certificates

Gateway certificate allowlist entries now need valid dates and strong root certificates, and the hostname must match exactly

You'll notice Improvements
JSON All of v2.1.309
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Gateway AuthArea: what it touches
ImprovementsKind: in v2.1.309,
ImprovementsSection of the release

Unclear Which gateway setups use this allowlist, and so who is affected, is not stated.

What

An organization can give Claude Code a list of root certificates (the certificates that vouch for a server's identity) to trust when it connects through a gateway. Claude Code now checks that list more strictly:

  • An entry only counts if its expiry date is in the future and no more than about a year past when Claude Code was built.
  • A listed root certificate is skipped if it is a public one, is not allowed to vouch for other certificates, or uses a weak key.
  • When only one root is trusted, the server's certificate must name the exact hostname in its list of names it is valid for.
Why

This makes it harder for a wrong or weak certificate to be trusted, and an entry that used to be accepted may now be skipped.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich gateway setups use this allowlist, and so who is affected, is not stated.

See this entry in the whole of v2.1.309 →

Feedback