Codify — Article

Limits federal funding for U.S. first-use nuclear strikes, adds certification to congressional leaders

Conditions DoD spending on a pre-strike certification to top Congressional leaders, with narrow operational exceptions for declared war, confirmed attack, and launch-on-warning.

The Brief

The Nuclear First-Strike Security Act of 2025 conditions federal spending for any U.S. first-use nuclear strike on two requirements: a Presidential determination that the strike is in the national interest, and, with limited exceptions, a written certification from the Secretary of Defense delivered to five top Congressional leaders no more than seven days before the strike. If those conditions are not satisfied, funds "authorized to be appropriated for any fiscal year" cannot be obligated or expended to carry out the strike.

The bill narrows the operational meaning of first-use by tying it to whether the Secretary of Defense and the Chairman of the Joint Chiefs of Staff have jointly confirmed that the foreign country has conducted a nuclear attack. It also enumerates three exceptions—an act of Congress declaring war, an actual nuclear detonation on U.S. or allied territory, and launch-on-warning detections—each of which removes the pre-strike certification requirement.

The statute thus creates a funding-based check on executive action while preserving specific rapid-response paths, raising immediate operational and legal implementation questions for the Department of Defense, the White House, and intelligence and attribution processes.

At a Glance

What It Does

The bill prohibits use of funds to conduct a U.S. first-use nuclear strike unless the President authorizes the strike and, except in three narrow scenarios, the Secretary of Defense submits a certification to five Congressional leaders within seven days before the strike. It defines key terms—‘first-use nuclear strike,’ ‘launch-on-warning scenario,’ ‘nuclear attack,’ and a list of named U.S. allies.

Who It Affects

The Department of Defense, the President’s national security apparatus, and military planners in U.S. nuclear command-and-control structures face new funding-based constraints. Congressional leadership (Speaker, House Majority and Minority Leaders, Senate Majority and Minority Leaders) become formal recipients of operational certifications.

Why It Matters

This is a statutory mechanism to limit executive flexibility on first-use through appropriations language rather than operational rules—shifting some oversight leverage into funding law. That combination directly affects deterrence signaling, operational timelines, and how the executive documents and shares decision logic with Congress.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

The bill does not prohibit the President from ordering a nuclear strike; it blocks federal funds from being used for a first-use nuclear strike unless two conditions are met: the President decides the strike is in the United States’ best interest, and the Secretary of Defense sends a written certification to five named Congressional leaders within a time window specified by the statute. The funding restriction operates across "amounts authorized to be appropriated for any fiscal year," which means the statutory lever is budgetary—if the certification is not in place, the Department cannot legally obligate or spend appropriated resources to carry out a qualifying first-use strike.

The statute narrows what counts as "first-use" by making it conditional on the absence of a joint confirmation from the Secretary of Defense and the Chairman of the Joint Chiefs that the foreign country has already conducted a nuclear attack. That makes the Secretary of Defense and the Chairman of the Joint Chiefs a formal, legal check in the attribution/confirmation chain: their joint confirmation converts an action from "first-use" into a retaliatory response, which carries different funding rules.

The bill also lists specific allies—NATO members, Japan, the Republic of Korea, and Australia—so the term "ally" is not open-ended.Operational exceptions preserve immediate executive responses in three circumstances. If Congress has declared war, the certification rule does not apply.

If one or more nuclear detonations have already occurred on U.S. or allied territory (the bill’s definition of "nuclear attack"), the certification is waived. Finally, the bill exempts "launch-on-warning" cases where early warning systems detect a missile trajectory that would impact U.S. or allied territory.

Each exception is narrow and fact-dependent, meaning much of how the statute works in practice will rest on detection systems, attribution protocols, and the timing of the certification relative to decision and launch timelines.Because the mechanism is a limitation on obligation and expenditure of appropriated funds, it functions as a compliance and auditing hook: absent the required certification, DoD would face a legal bar to drawing down funds to execute the strike. That creates both an enforcement pathway (through DoD budgeting and Comptroller controls) and an operational tension: certification transmission and any challenges to its sufficiency could introduce delays or political exposures into decisions that in some scenarios require immediate action.

The Five Things You Need to Know

1

The bill conditions use of any amounts "authorized to be appropriated for any fiscal year" for a first-use nuclear strike on a Presidential decision and a Secretary of Defense certification submitted to five Congressional leaders within seven days prior to the strike.

2

The certification must be delivered to the Speaker of the House, the House Majority Leader, the House Minority Leader, the Senate Majority Leader, and the Senate Minority Leader — the statute names those five recipients explicitly.

3

Three exceptions remove the certification requirement: (1) a Congressional declaration of war, (2) an actual nuclear detonation on U.S. or allied territory (a defined "nuclear attack"), and (3) a launch-on-warning scenario where early warning systems indicate an incoming missile trajectory.

4

The bill defines "first-use nuclear strike" as any U.S. nuclear attack against a foreign country occurring where the Secretary of Defense and the Chairman of the Joint Chiefs have not jointly confirmed that the foreign country has already conducted a nuclear attack.

5

Because the restriction is on obligation and expenditure of authorized appropriations, DoD Comptrollers and accounting systems are the primary enforcement mechanisms: absent certification, funds to execute a qualifying strike would be blocked.

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Section 1

Short title

Provides the Act’s name: the "Nuclear First-Strike Security Act of 2025." This is purely titular but signals the statute’s intent to focus on first-use policy and to do so through statutory language tied to funding controls.

Section 2(a)

Primary funding limitation and dual conditions for action

Establishes the statute’s core rule: no funds authorized for any fiscal year may be obligated or expended to conduct a first-use nuclear strike unless the President decides the strike is in the U.S. best interests and the Secretary of Defense submits a certification to specified Congressional leaders no more than seven days before the strike. Practically, this converts what would be an operational decision into one that must be accompanied by a documented, time-limited certification for budgetary compliance. The accounting phrase—"obligated or expended"—targets execution-level funding, so DoD financial officers will need procedures to treat an absent or defective certification as a legal bar to launching with allocated funds.

Section 2(b)

Narrow operational exceptions

Carves out three scenarios where the seven-day pre-strike certification is not required: (1) when Congress enacts a declaration of war, (2) when a foreign actor has conducted a nuclear attack as defined by the statute (one or more nuclear detonations on U.S. or allied territory), and (3) during a launch-on-warning scenario detected by early warning systems. Each exception is intended to preserve immediate-response authority in the most acute wartime or imminent-attack situations, but each also depends on real-time detection, attribution, or congressional action—areas where operational and legal ambiguity may arise.

1 more section
Section 2(c)

Definitions that shape triggers and scope

Defines ‘‘ally of the United States’’ to include NATO members, Japan, the Republic of Korea, and Australia; "first-use nuclear strike" in relation to the absence of a joint confirmation by the Secretary of Defense and the CJCS; "launch-on-warning scenario" tied to early-warning detections of missiles on impact trajectories; and "nuclear attack" as one or more actual nuclear detonations on U.S. or allied territory. These definitions are operationally consequential: they fix attribution and ally status in statute, narrow the universe of exempted events, and place specific responsibilities on senior Department of Defense officials for joint confirmation.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Defense across all five countries.

Explore Defense in Codify Search →

Who Benefits and Who Bears the Cost

Every bill creates winners and losers. Here's who stands to gain and who bears the cost.

Who Benefits

  • Congressional leadership — gains a formal, statutory notification role and a funding-based oversight lever in the most consequential executive military decision, increasing institutional visibility into first-use decisions.
  • Arms-control and nonproliferation advocates — receive a statutory constraint on unilateral first-use, which can be used to argue for reduced risk of preemptive nuclear employment and greater deliberation.
  • Allied governments and populations named in the statute (NATO members, Japan, ROK, Australia) — benefit from a clearer, statutory categorization that influences whether U.S. action will be treated as first-use or retaliatory, with attendant political and diplomatic signaling.

Who Bears the Cost

  • The Executive Branch (President, National Security Council) — faces reduced procedural flexibility and an additional step (and disclosure to Congressional leaders) before using appropriated funds for first-use, potentially exposing deliberations and compressing crisis decision timelines.
  • Department of Defense operations and planners — must adapt command-and-control, legal, and financial compliance processes to the certification timeline, and Comptrollers may need new procedures to withhold funds absent certification.
  • Military commanders and nuclear forces — could encounter tighter constraints on pre-planned options, especially in scenarios where attribution is ambiguous or warnings compress decision windows, increasing operational risk or forcing doctrinal adjustments.

Key Issues

The Core Tension

The central tension is between democratic oversight and operational responsiveness: the bill advances congressional visibility and a budgetary brake on first-use decisions, but when nuclear decision timelines are compressed, any statutory requirement to certify to political leaders risks delaying action, exposing classified deliberations, or forcing the Executive to rely on narrow exceptions—each outcome undermines either accountability or immediate national defense.

The bill uses appropriations law to induce compliance rather than directly limiting presidential orders. That creates an enforcement pathway through DoD budget and accounting systems, but it also opens questions about how to handle time-critical launches when funds are technically available in some accounts but legally barred for the specified purpose.

Fungibility of funds, the timing of obligations, and the role of the DoD Comptroller will determine whether the restriction is a robust check or a paper constraint.

Definitions and confirmation mechanics create practical ambiguities. The statute makes joint confirmation by the Secretary of Defense and the Chairman of the Joint Chiefs a switch that converts "first-use" into "retaliation," but it does not set evidentiary standards, attribution processes, or timelines for that joint confirmation.

Similarly, the launch-on-warning exception presumes reliable early-warning detection and confidence in trajectory assessment — both of which have historically produced false alarms and would require hardened, well-documented protocols to be safely relied upon. These gaps mean agencies will need implementing guidance, interagency rules for attribution, and contingency budgeting practices to translate the statute into operable procedures.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.