TRENDING
Close-up of an iridescent teal duck feather with a brown edge against a blurred green background
November 13, 2026
Apache Patches a Critical mod_http2 RCE Found Independently by Anthropic’s Scanner and Google Researchers, but 2.4.70 Shipped Nearly Five Days Earlier Without the Fix and the One-Line Patch Was Public for About 58 Hours Before the Advisory
An open Pacific oyster shell resting on a wooden chopping board
November 13, 2026
CNCF’s OpenShell-on-Kubernetes Guide Turns Agent Sandboxing Into a Two-Layer Split, but the Demo’s Seven Kyverno Policies Admit Secret Volumes, Oversized Init Containers and Unconfined Seccomp, and the OpenShell Release It Describes Is Five Behind the Current One
Close-up of the white locking bars and cam handles on the closed doors of a grey intermodal shipping container
November 13, 2026
Red Hat Published Eight Fixed Quay Releases Within Two Hours of Its CVSS 9.8 Signing-Key Advisory, but the CVE Page Still Lists No Fix, and the Sibling 9.9 Flaw’s Page Names Those Releases While None of Their Advisories Lists It
A white life ring hanging on a wooden post above an empty sandy beach and calm blue water, a rescue tool kept within reach before anyone needs it
November 13, 2026
How to Recover Lost Commits and Files in Git With reflog and fsck, and Snapshot Uncommitted Work Before a Script or AI Agent Can Wipe It
Three meerkats standing upright on a red sand mound at dusk, each looking in a slightly different direction
November 13, 2026
Cloudflare’s QuePaxa Post Turns Leader Elections Into a Hedging Delay, but in a Simulation of the Paper’s Protocol a Five-Millisecond Hedge Costs Every Slot Its Fast Path, and the 2020 Outage It Cites Lasted Six Hours Because Database Replicas Had to Be Rebuilt
13 Nov 2026
SXZ.io SXZ.io
  • Home
Search the Site
Popular Searches:
Technology Amazon AI
Recent Posts
A hazel dormouse climbing among green leaves and orange berries, a visual pun on dormant neurons
Microsoft’s Lazarus Post Turns “Fewer Than 10 Dormant Neurons” Into an Agent Backdoor, but the Paper Measured a Harmless Marker, Qwen Reached 51% on the Same 23 Samples, and the 91.4% Detector Was Scored on 35 Edited Checkpoints From the Attack’s Own Family
November 13, 2026
A coal miner’s hard hat with an electric headlamp resting on a dark cloth
Attackers Put Miners on 21 N-central Servers Within Nine Hours of a Public Exploit, 19 of Them on the Hotfix 2 Build, and Apache Does Not Expect to Release a Fixed Axis 1 for the Flaw That Starts the Chain
November 13, 2026
Concrete dam wall with a footbridge along its crest holding back a calm reservoir below tree-covered hills, with a few people standing at the near end of the walkway
How to Shut Down a FastAPI Service Without Dropping Requests: Handle the Stop Signal, Drain Before You Close, and Survive a Rolling Restart Behind nginx
November 12, 2026
SXZ.io SXZ.io
  • Home

Categories

Articles 297 Posts
News 302 Posts
Learning Hub 268 Posts
Home/Articles/The D.C. Circuit’s 2-1 Ruling Turns Anthropic’s Own Guardrails Into a Supply-Chain Risk
Articles

The D.C. Circuit’s 2-1 Ruling Turns Anthropic’s Own Guardrails Into a Supply-Chain Risk

A federal appeals court sided with the Pentagon in a case separate from the one Anthropic already won in California, ruling that Claude's own safety restrictions can count as evidence of a...

September 25, 2026 5 Min Read
69

A federal appeals court ruled Friday that the Pentagon was within its rights to label Anthropic a “supply chain risk,” handing the Department of Defense a win in a legal fight that, a month earlier, had gone the opposite way in a different courtroom entirely. Judges on the U.S. Court of Appeals for the District of Columbia Circuit split 2-1 in the government’s favor, rejecting Anthropic’s challenge and leaving the Pentagon free to keep Claude off its own systems and bar the Defense Department from using Anthropic’s products.

Table Of Content

  • Two Lawsuits, One Fight, Two Outcomes
  • What ‘What, Not Why’ Means for a Safety Feature
  • A Dissent, and an Unsettled Next Move

The ruling does not disturb the case Anthropic has already won. It is a separate lawsuit, filed the same month in a different court, built around what the Associated Press describes as “a different rule the Pentagon was using to try to declare Anthropic a supply chain risk.” Two federal courts looked at the same underlying dispute between an AI lab and its would-be biggest customer and reached opposite conclusions, and the reason why says less about who is right than about how narrow a legal needle a “supply chain risk” designation asks judges to thread when the thing being restricted is a piece of software’s own safety design.

Two Lawsuits, One Fight, Two Outcomes

The dispute traces back to February 2026, when Defense Secretary Pete Hegseth gave Anthropic three days to agree to “all lawful uses” of its technology, or be designated a supply chain risk. Anthropic refused to drop the restrictions it had built into Claude against fully autonomous weapons and mass domestic surveillance. President Donald Trump and Hegseth followed through, ordering every federal agency to stop using Anthropic’s products and barring defense contractors from doing any business with the company at all, even work with nothing to do with the Pentagon.

Anthropic responded by filing two separate complaints that same March, one in the Northern District of California and one in Washington, D.C., according to TechCrunch‘s reporting at the time. The California case reached a verdict first. On the night of August 27, U.S. District Judge Rita Lin ruled that the designation amounted to “unlawful retaliation in violation of the First Amendment” against Anthropic for publicly criticizing the Pentagon’s approach to military AI, a ruling sxz.io covered in depth at the time. TechCrunch noted at the time that the D.C. suit “is still ongoing.”

It has now concluded, and not in Anthropic’s favor. Judges Gregory G. Katsas and Neomi Rao, both nominated to the D.C. Circuit by Trump, formed the majority. Judge Karen LeCraft Henderson, nominated by President George H.W. Bush in 1990, dissented. The panel’s makeup meant the same underlying grievance produced opposite outcomes in front of two different courts, weighing two different legal theories against the same designation.

What ‘What, Not Why’ Means for a Safety Feature

The D.C. Circuit’s majority did not dispute the facts Judge Lin relied on. According to the Associated Press wire report carried by KSAT, the judges said they had “no reason to doubt” that Anthropic acts with “noble intentions” in restricting what Claude will do, and they had “no quarrel” with the conclusions the California court reached in the separate case. Where they parted ways was on what the law actually requires for a supply chain risk finding to stand: not a bad motive on Anthropic’s part, but simply “on what Anthropic does, not why Anthropic does it.”

That standard turned Anthropic’s own engineering choices into the government’s exhibit. The majority opinion, written by Katsas, noted that “by Anthropic’s own admission, the company encodes restrictions into Claude that prevent the model from performing tasks that Anthropic wishes to prevent.” From there, the reasoning followed a straight line: “The Department reasonably feared that Anthropic might manipulate Claude’s design to prevent it from performing national-security functions that the Department deems contractually authorized and necessary,” Katsas wrote, concluding the Pentagon had “ample support” for its position. The same safety guardrails Anthropic built specifically to keep Claude from being weaponized against domestic surveillance or autonomous lethal use became, in the majority’s reading, proof that the company might one day withhold a capability the Pentagon considered its own to command.

It is a distinction with real teeth for any AI vendor doing business with the federal government. A company cannot simply avoid the “why” question by having good intentions; under this reading, the mere technical capacity to restrict a model’s behavior, regardless of the reason it was built, can itself support a national-security risk finding if a customer decides it does not like being told no.

A Dissent, and an Unsettled Next Move

Judge Henderson’s dissent was not detailed in the AP’s account beyond her vote, but her presence as the lone holdout, and the one judge on the panel not appointed by Trump, underscores how contested the “what, not why” framework is even among judges who agree on the underlying facts. Pentagon spokesman Sean Parnell called the outcome a full vindication, writing that “today’s DC Circuit Court ruling completely validates the Department’s position,” according to the AP.

Anthropic was less conciliatory. A company spokesperson said in a written statement that Anthropic “respectfully disagrees” with the court’s decision. “Another federal court has already held the government’s parallel designation unlawful,” the statement continued. “We remain confident in our position and are considering all options, including further review.” That leaves open the possibility of a petition for rehearing en banc before the full D.C. Circuit, or an eventual appeal to the Supreme Court, either of which could take months to resolve while the practical restrictions imposed by Friday’s ruling stay in effect.

For now, the two rulings coexist uneasily. The California decision, which sxz.io covered when it came down in August, blocks the Pentagon from punishing Anthropic for its public criticism. The D.C. ruling lets the Pentagon’s underlying supply chain risk label stand on entirely separate grounds, meaning the restrictions on Claude that took effect in March remain in force for now, regardless of which theory a future court finds more persuasive. Any AI company weighing whether to hold firm on safety commitments in a high-stakes government contract now has a live example of how that choice can be read in court: not as evidence of good faith, but as evidence of exactly the kind of control a national-security customer says it cannot accept.

Tags:

AI GovernanceAI PolicyAnthropicNational SecurityPentagon

Share

The New York Stock Exchange building facade with a large American flag, where Nscale plans to list its shares
Previous Post

Nscale Raises $3.36 Billion Ahead of a Wall Street IPO Built on Two Customers

A staircase of sequential canal lock chambers at Bingley Five Rise Locks, each gate validating the water level before the next stage
Next Post

How to Build a Multi-Stage AI Agent Pipeline in Python to Stop Errors From Compounding

No Comment! Be the first one.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Latest
13 Nov
Microsoft’s Lazarus Post Turns “Fewer Than 10 Dormant Neurons” Into an Agent Backdoor, but the Paper Measured a Harmless Marker, Qwen Reached 51% on the Same 23 Samples, and the 91.4% Detector Was Scored on 35 Edited Checkpoints From the Attack’s Own Family
13 Nov
Attackers Put Miners on 21 N-central Servers Within Nine Hours of a Public Exploit, 19 of Them on the Hotfix 2 Build, and Apache Does Not Expect to Release a Fixed Axis 1 for the Flaw That Starts the Chain
Trending
November 13, 2026
Microsoft’s Lazarus Post Turns “Fewer Than 10 Dormant Neurons” Into an Agent Backdoor, but the Paper Measured a Harmless Marker, Qwen Reached 51% on the Same 23 Samples, and the 91.4% Detector Was Scored on 35 Edited Checkpoints From the Attack’s Own Family
November 13, 2026
Attackers Put Miners on 21 N-central Servers Within Nine Hours of a Public Exploit, 19 of Them on the Hotfix 2 Build, and Apache Does Not Expect to Release a Fixed Axis 1 for the Flaw That Starts the Chain
November 12, 2026
How to Shut Down a FastAPI Service Without Dropping Requests: Handle the Stop Signal, Drain Before You Close, and Survive a Rolling Restart Behind nginx
November 12, 2026
Apache Patches a Critical mod_http2 RCE Found Independently by Anthropic’s Scanner and Google Researchers, but 2.4.70 Shipped Nearly Five Days Earlier Without the Fix and the One-Line Patch Was Public for About 58 Hours Before the Advisory
November 12, 2026
CNCF’s OpenShell-on-Kubernetes Guide Turns Agent Sandboxing Into a Two-Layer Split, but the Demo’s Seven Kyverno Policies Admit Secret Volumes, Oversized Init Containers and Unconfined Seccomp, and the OpenShell Release It Describes Is Five Behind the Current One
November 12, 2026
Red Hat Published Eight Fixed Quay Releases Within Two Hours of Its CVSS 9.8 Signing-Key Advisory, but the CVE Page Still Lists No Fix, and the Sibling 9.9 Flaw’s Page Names Those Releases While None of Their Advisories Lists It

Related Posts

Blue-lit server racks in a modern data center, illustrating the compute infrastructure behind the AI boom.
Articles

The AI Boom Is Spending Real Money Before Proving Real Returns

June 7, 2026
Technician working with a laptop beside server racks, representing enterprise AI retrieval infrastructure
Articles

Google’s Agentic RAG Push Makes Enterprise AI Less of a One-Shot Guess

June 7, 2026
A person with a laptop and smartphone, representing digital attention and AI-assisted work
Articles

AI Chatbots Are Making Attention a Design Problem

June 7, 2026
A customer-support representative wearing a headset against a dark studio background.
Articles

The Meta AI Support Hack Was a Plain Old Authorization Failure

June 7, 2026
SXZ.io SXZ.io
  • [email protected]

Categories

Articles
Learning Hub
News

All Rights Reserved by SXZ.io ©2026