‘Imminent Threat’ Has No Legal Definition — and Presidents Know It

GovFacts

Last updated 1 month ago. Our resources are updated regularly but please keep in mind that links, programs, policies, and contact information do change.

Search the entire text of the War Powers Resolution of 1973 and you will not find a definition of “imminent threat.” The phrase appears four times in the statute, never explained. Congress wrote a law to limit presidential war-making, deliberately left the triggering condition undefined, and then spent the next five decades watching presidents drive military operations through that gap.

On March 4, 2026, the Senate voted 47-53 to block a war powers resolution that would have halted further U.S. Military strikes against Iran. Only Senator Rand Paul (R-Ky.) crossed party lines to support the Democratic-backed measure, while Senator John Fetterman (D-Pa.) voted against it. But the vote count, close as it was, hides the more interesting problem underneath.

According to Senator Chris Murphy’s public characterization of a classified Senate briefing, the Trump administration cited an imminent Iranian attack to justify its war powers notification — but when pressed, Murphy said, could produce no evidence to support that claim. “As my colleagues have amply demonstrated,” Murphy said on the Senate floor, “the administration and their shifting set of rationales, and even in a classified setting, could produce no evidence, none that the U.S. Was under an imminent threat of attack from Iran.”

Murphy’s account should be understood as one senator’s description of a closed proceeding. The administration disputes this description. The classified nature of the briefing makes independent verification impossible. Other senators who attended the same briefing may have judged the evidence differently. Murphy, a Democrat who publicly opposed the strikes, had an obvious political reason to describe the briefing as empty.

What can be independently checked, and is separately important, is that the administration’s senior officials gave contradictory public accounts of the legal basis for the operation. That problem does not depend on Murphy’s closed-session account.

But what makes Murphy’s accusation more than a partisan attack is this: no institution in the American system has ever agreed on what evidence would be enough to prove an imminent threat in the first place. Not Congress, not the courts, not the executive branch itself. The standard does not exist. Presidents know it does not exist. And the absence is not an accident.

The War Powers Resolution’s Undefined Triggering Condition

The War Powers Resolution sets up a framework that sounds, on paper, like a genuine constraint. Under 50 U.S.C. Section 1541, the president may send armed forces into hostilities only under a declaration of war, specific statutory authorization, or a national emergency created by attack upon the United States or its forces. The first two require Congress. The third is the emergency exception.

What the statute leaves out is everything that would make the standard enforceable: when an attack is “imminent” rather than merely possible, what level of certainty the president must have, what evidence Congress or the courts can demand, or who gets to decide whether the emergency exists.

The word “imminent” appears in the statute’s description of when Congress should be consulted. But nowhere does it establish who makes that call. It does not specify what proof is required, or whether the decision is reviewable.

When Congress passed the resolution in 1973 over President Nixon’s veto, this void was not an oversight. Senate debate from that period shows members knew they were creating a boundary without defining it. Some wanted strict requirements. Others worried that defining “imminent” too precisely would freeze the president in genuine emergencies where every hour mattered.

The compromise was to limit the president through procedure: 48-hour notification, regular consultation, a 60-day clock. But the core trigger was left vague. A political solution to a constitutional problem.

No president since 1973 has terminated a military operation in response to a war powers resolution. The statute’s procedural requirements have not prevented any of the major military actions undertaken in that period.

The executive branch noticed immediately. Harvard Law Professor Jack Goldsmith, who served as Assistant Attorney General in charge of the Office of Legal Counsel under President George W. Bush, has noted that the executive branch’s internal legal advisers have consistently read presidential war powers broadly. They treat vague statutory language as grants of authority rather than limits.

The theory that developed over decades holds that the president may use force alone whenever the president decides it serves the national interest and the force does not rise to the level of “war in the constitutional sense” (meaning a large-scale, sustained conflict that would require a formal declaration). That test gives so much weight to presidential judgment that it has allowed sustained bombing campaigns, drone strikes across multiple countries, and military strikes from Libya to Yemen to Somalia to Syria — all without a single court ever saying no.

For a fuller look at how this framework operates in practice, our earlier explanation of when presidents can strike first covers the constitutional architecture in detail.

Secretary of State Marco Rubio gave public accounts of why the United States struck Iran on February 28, 2026, that are not compatible — accounts that, according to reporting on his statements, shifted between Monday and Tuesday of that week.

Version one, delivered at a Monday press conference: “We knew that there was going to be an Israeli action. We knew that that would precipitate an attack against American forces, and we knew that if we didn’t preemptively go after them before they launched those attacks, we would suffer higher casualties.” In this account, the imminent threat was not mainly Iranian in origin. It was the expected Iranian response to an Israeli strike. This was a reactive threat dependent on Israel acting first.

Version two, offered by Tuesday afternoon: “The decision to strike came from Trump. He made the decision to go first because he concluded that we were not going to get hit first. He was not going to run the risk that they could attack us before we could hit them.” This version places the threat squarely on Iran’s own independent preparations. It describes a proactive self-defense scenario with no Israeli action required.

The two accounts describe legally different scenarios: one in which the United States was expecting an Iranian response to Israeli action, and one in which Iran was independently preparing to strike American forces.

If the first version is accurate, the U.S. Was stepping into an Israeli-Iranian conflict rather than responding to a direct attack on its own forces. That is a weaker self-defense claim.

If the second is accurate, the claim is stronger, but it requires evidence that Iran was preparing such an attack. According to Murphy’s characterization of the classified briefing, no such evidence was presented. The administration disputes that account, and the closed nature of the proceeding prevents independent confirmation. Whether the briefing resolved this ambiguity is unknown. But the public contradiction makes it harder for Congress to assess the legal basis for the operation on the record available to it.

Reports suggest that at the same classified briefing, Trump administration officials declined to rule out the use of ground troops in Iran. That refusal carries its own legal significance, because the War Powers Resolution’s procedural requirements differ depending on the scope of military commitment. An administration that leaves open the possibility of ground deployments while keeping that information from public congressional debate is signaling an expansion of the operation without giving Congress the information it would need to make an informed judgment about authorizing it. Our coverage of whether the joint U.S.-Israel strikes required separate congressional approval explores that threshold question directly.

How the Political Question Doctrine Has Blocked Judicial Review of War Powers

The political question doctrine is a judge-made rule holding that certain disputes are political in nature and not suitable for courts to resolve. In the war powers context, it has acted as a near-total barrier to judicial review for six decades.

The landmark case is Campbell v. Clinton, a 2000 decision by the U.S. Court of Appeals for the D.C. Circuit. Democratic congressmen sued President Clinton to stop his bombing campaign in Yugoslavia. They argued he had violated the War Powers Resolution and the Constitution by starting offensive military operations without congressional authorization. The court dismissed the lawsuit. The judges could not agree on why.

One held that the case presented a political question courts cannot review. Congress had appropriated money for the campaign and voted to set aside and kill a war powers resolution — though the court dismissed the case on standing grounds without reaching the merits of whether those congressional actions constituted implied agreement with the bombing.

A second argued that courts could not determine whether the bombing counted as “war” within the meaning of the Constitution’s Declaration of War Clause without making a judgment with no objective legal test to guide it. A third concluded the plaintiffs lacked standing, reasoning that the alleged harm was not sufficiently particularized to individual members — though the precise contours of that standing analysis require verification against the full opinion text.

Different reasoning, same result: courts would not review the president’s military decisions.

In Kucinich v. Obama (2011), when congressmen sued to prevent airstrikes in Libya, the court dismissed the case on the grounds that it was moot. The operation was already over, so there was nothing left for a court to stop. Because the operation was brief and had already concluded, there was no live case or controversy to resolve. The court never ruled on whether the strikes violated the War Powers Resolution.

Judge Silberman, writing separately in Campbell, spelled out the logic that keeps the void from ever being filled: “the statutory threshold standard is not precise enough and too obviously calls for a political judgment to be one suitable for judicial determination.” Read that sentence carefully. Because Congress did not define “imminent threat” precisely, courts refuse to define it. Because courts refuse to define it, presidents define it themselves. The circularity is perfect. It is perfectly favorable to executive power.

Harold Koh, the former Legal Adviser to the State Department under President Obama and now a professor at Yale Law School, has written at length on how the absence of judicial review has allowed the executive branch’s war powers interpretations to grow across administrations. The executive branch’s answer to what counts as a sufficient threat has consistently been: whatever the president says.

Four Contested Imminent Threat Claims, Zero Judicial Interventions

The Iran dispute is the fourth major iteration of this pattern in sixty years. Each time, an administration asserted an imminent threat. Each time, the evidence was contested or absent. Each time, no court intervened.

August 4, 1964: President Johnson reported that North Vietnamese torpedo boats had attacked the USS Maddox a second time and asked Congress for immediate authorization to carry out retaliatory airstrikes. Congress approved the Gulf of Tonkin Resolution with overwhelming support. The resolution served as the legal basis for escalating the Vietnam War until its repeal in January 1971 — roughly six to seven years, not the full duration of U.S. military involvement.

What happened on August 4? Decades later, declassified NSA documents revealed that the second attack did not occur. NSA analysts had intercepted partial messages that the Johnson administration misread, or manipulated, as evidence of a North Vietnamese attack. As one NSA official later summarized: “In truth, Hanoi’s navy was engaged in nothing that night but the salvage” of damaged boats from the first attack. The Senate Foreign Relations Committee later found that the administration had misrepresented facts to Congress. Congress had voted to authorize an escalation based on a false premise. Over 58,000 American soldiers died.

2002: The Bush administration claimed Saddam Hussein possessed weapons of mass destruction that posed an imminent threat to the United States and its allies. The October 2002 National Intelligence Estimate stated that Iraq appeared to be rebuilding its nuclear weapons program and possessed active biological weapons laboratories. Congress voted to authorize military force. No active WMD programs or significant current stockpiles were found, though some degraded legacy chemical weapons from the Iran-Iraq War era were later discovered.

The Senate Intelligence Committee’s Phase II report, released in 2007, concluded that most of the major key judgments in the NIE “either overstated, or were not supported by, the underlying intelligence reporting.” The intelligence community had adopted “untested and, in hindsight, unwarranted assumptions” and failed to clearly explain the uncertainties behind its conclusions. More than 4,400 American service members were killed. Trillions of dollars were spent. No court intervened.

January 2020: The Trump administration claimed that General Qasem Soleimani was planning “imminent attacks” against American forces and facilities. Secretary of State Mike Pompeo said Soleimani was “actively developing plans to attack American diplomats and service members in Iraq and throughout the region” and that attacks were “imminent” — though some subsequent accounts paraphrased his language more broadly. A Department of Justice memo released under the Freedom of Information Act following the killing concluded the strike was lawful under Article II as a legitimate act of self-defense.

But the memo’s released portions do not clearly show that Soleimani had an attack underway or planned for a specific time or place. Reports later suggested that the evidence of an imminent attack was very weak, with at least one account describing it in strikingly thin terms — though the specific phrasing varies by source and no single publication’s wording should be treated as definitive. Some administration officials privately acknowledged the imminent threat assessment was overstated. No court reviewed whether the strike met the international law standard for self-defense. That standard requires that the threat be “instant, overwhelming, leaving no choice of means, and no moment for deliberation.” This formulation is known as the Caroline doctrine, named for an 1837 border dispute.

The table below shows how each administration’s imminent threat claim fared against subsequent scrutiny.

Presidential “imminent threat” claims and subsequent findings, 1964-2026
IncidentYearAdministration’s ClaimSubsequent FindingCourt Review?
Gulf of Tonkin1964Second North Vietnamese attack on USS MaddoxNSA declassified documents showed the second attack did not occurNo
Iraq WMDs2002-03Active WMD programs posing imminent threatSenate Intelligence Committee found NIE overstated or unsupported by underlying intelligenceNo
Soleimani killing2020Imminent attacks on American forces and facilitiesReleased OLC memo did not clearly establish specific planned attack; evidence described as “razor thin”No
Iran strikes2026Imminent Iranian attack on U.S. ForcesSecretary Rubio offered contradictory public accounts of the legal basis for the operation; Senator Murphy’s characterization of the classified briefing, disputed by the administration, was that supporting evidence for an imminent threat was not producedNo

Sources: NSA declassified Gulf of Tonkin documents; Senate Intelligence Committee Phase II Report; DOJ Office of Legal Counsel memorandum on Soleimani strike; Sen. Murphy’s statement on Iran briefing.

Four cases. Four contested or absent threat assessments. Zero judicial interventions. The pattern is not a coincidence.

One interpretation, put forward by scholars including Curtis Bradley and Jack Goldsmith, holds that it reflects a functional constitutional settlement: fifty years of consistent executive action, congressional appropriations, and judicial non-intervention together constitute democratic acceptance of executive primacy in national security matters, not a design failure.

A competing interpretation holds that the pattern reflects a structural void. Congressional acquiescence driven by partisan calculation and judicial inaction driven by the political question doctrine have together allowed the executive branch to expand its war-making authority beyond what the constitutional text, read in light of its original purpose, can support. The difference between these interpretations is not merely academic. It determines whether the solution lies in better political will within the existing framework, or in structural reform of the framework itself.

Congress’s Available Tools and Why They Have Not Worked

The statute gives Congress a 60-day clock under 50 U.S.C. 1544. After the president files a notification of military action, Congress must either declare war, authorize the specific use of force, or extend the deadline. If Congress does not act, the president “shall terminate” the military operation. Sounds like a real constraint.

Except: the president can veto any resolution Congress passes. Overriding that veto requires a two-thirds supermajority in both chambers. In the March 2026 votes, the Senate war powers resolution failed 47-53. Even if it had passed, it would have needed to survive a presidential veto.

The House saw a bipartisan Khanna-Massie resolution calling for immediate withdrawal fail 212-219. A competing measure from Democratic Representative Josh Gottheimer proposed giving the president 30 additional days to continue operations unless Congress authorized the war. That measure would have effectively handed over Congress’s war-making authority for another month. As Louis Fisher, the leading historian of congressional war powers, has documented, no president since 1973 has complied with a war powers resolution directing withdrawal of forces. The 60-day clock has never stopped a military operation.

Congress also theoretically holds the power of the purse. It could refuse to appropriate funds for unauthorized military operations. During the Vietnam War, Congress continued appropriating funds even after the Gulf of Tonkin Resolution was repealed in 1971. Courts treated this as after-the-fact approval of the conflict. During the Iraq War, appropriations continued as skepticism grew. The defunding power exists in theory. It has never been effectively used.

Then there is the information problem. Murphy’s characterization of the classified briefing — that the administration “could produce no evidence, none that the U.S. Was under an imminent threat” — is disputed by the administration and cannot be independently verified. But the structural problem it points to is real regardless of how that specific dispute is resolved.

If the threat assessment rests on classified intelligence that Congress cannot see in open session, how can Congress fulfill its constitutional role as judge of whether war powers were properly used? And if Congress subpoenas classified intelligence and the administration refuses on national security grounds, who decides whether the refusal is justified?

The Justice Department’s internal legal office has maintained that executive privilege protects classified national security information from congressional subpoenas in the context of military decisions. Executive privilege is the president’s claimed legal right to withhold sensitive information from Congress. Courts have been reluctant to force disclosure. The result is that Congress must vote on whether to authorize ongoing military operations without reliable access to the factual basis for the president’s threat claim.

For a detailed look at the practical tools Congress has available and why they keep falling short, see our analysis of whether Congress can stop a president from launching military strikes.

The Constitutional and Historical Arguments for Presidential War Powers

The administration’s position is not a frivolous one. It is rooted in constitutional text, historical practice, and consistent executive branch interpretation across administrations of both parties. The strongest version of this argument deserves serious engagement before its limits are examined.

The constitutional text argument begins with Article II’s designation of the President as “Commander in Chief of the Army and Navy of the United States.” Originalist scholars Saikrishna Prakash and Michael Ramsey have argued, in a widely cited analysis in the Yale Law Journal, that the founding-era understanding of “executive power” included the handling of foreign relations and military operations.

They further argue that the Commander in Chief clause places operational control of armed forces exclusively in the executive. On this reading, Congress’s power to “declare war” was understood at the founding as a formal legal act recognizing a state of war between nations. It was not a requirement of prior authorization for every use of force.

The historical practice of the founding generation supports this reading. Washington sought and received explicit congressional authorization through acts passed in 1789 and 1790 before using force against Native American nations, and deferred to Congress when authorization was sought for offensive operations in 1792. Adams authorized naval hostilities with France in the Quasi-War without a formal declaration of war, though Congress did pass specific statutory authorizations for those naval hostilities — it was not purely executive action. Jefferson deployed the Navy against the Barbary pirates before Congress formally acted, but explicitly limited the mission to defensive operations only, then sought and received congressional authorization for offensive operations. If the Founders themselves did not treat the Declaration of War Clause as a prior-authorization requirement, the argument goes, the modern executive branch is not straying from original meaning by acting similarly.

The functional argument is equally serious. The Founders were designing for a world of sailing ships and weeks-long communication delays. Modern threat timelines, including ballistic missiles and cyberattacks capable of disabling critical infrastructure within minutes, make prior congressional authorization structurally impossible in ways the Founders could not have foreseen. Terrorist cells can also scatter if their planning is detected.

Requiring a floor debate and recorded vote before responding to an incoming missile is not a constitutional constraint; it is a formula for paralysis. The functional argument about modern threat timelines draws on the reality that some genuinely time-sensitive threats may require rapid executive action. Even scholars skeptical of broad executive power have acknowledged that some category of genuinely time-sensitive threats requires unilateral executive action.

The argument from constitutional settlement may be the most practically powerful. For fifty years, across administrations of both parties, presidents have used force without congressional declarations. Congress has appropriated funds for those operations. Courts have declined to intervene. No military operation has ever been halted by a war powers statute.

Scholars including Curtis Bradley and Jack Goldsmith have written that historical practice and congressional acquiescence inform constitutional meaning in war powers contexts. On this view, it is not a failure of the system but the system’s actual operating balance. It reflects democratic acceptance of executive primacy in security matters. The statute’s procedural requirements are the real constraint. Presidents who file 48-hour notifications and comply with the 60-day clock are operating within the law as it has been understood and practiced for half a century.

Administration supporters also point to the 2001 Authorization for Use of Military Force, passed in the days after September 11. It authorizes the president to use “all necessary and appropriate force” against those who planned, authorized, committed, or aided the September 11 attacks, or harbored such organizations. Iran has harbored terrorist organizations, the argument goes, so the 2001 AUMF could potentially reach Iranian-backed groups threatening U.S. Forces. Many legal scholars find this interpretation a stretch. But the executive branch has been stretching broad congressional authorizations for decades. Congress has continued appropriating funds for operations under those interpretations. Courts have sometimes read this as after-the-fact approval.

Former Senate Majority Leader Mitch McConnell said during the March 2026 Senate debate that the president has authority to use military force with or without congressional approval, while acknowledging that risks are involved. This position holds that the War Powers Resolution’s procedural requirements do not limit the president’s underlying constitutional power to act alone when the president decides such action is necessary. File the 48-hour notification, comply with the 60-day clock, and the law is satisfied.

These arguments have genuine force, and they explain why the executive authority position has had bipartisan support across administrations. But they do not resolve the specific legal problem presented by the Iran strikes, for reasons that go beyond the general debate about presidential war powers.

The originalist historical practice argument, Washington, Adams, Jefferson, involved force used against non-state actors, pirates, and frontier conflicts. It did not involve sustained bombing campaigns against a major regional state with whom the United States has no existing authorization for war.

The functional argument about modern threat timelines is strongest when the threat is genuinely imminent and time-sensitive. It is weakest when the administration itself cannot settle on a consistent account of the threat. The contradictions in Secretary Rubio’s public statements suggest the administration could not agree on whether the threat was reactive (expecting an Iranian response to Israeli action) or proactive (Iran’s independent preparations). A genuine time-sensitive emergency does not typically produce two incompatible public explanations within 24 hours.

The constitutional settlement argument, that fifty years of practice makes up democratic legitimacy, depends on the premise that congressional acquiescence is informed acquiescence. When the factual basis for the threat claim is classified and, according to at least some senators who attended the briefing, not adequately supported by evidence presented in that setting, the acquiescence is not meaningfully democratic. Congress cannot approve what it cannot evaluate.

The framers who wrote Article I’s declaration of war clause and Article II’s commander-in-chief clause were trying to create a system where those two provisions existed in tension, each checking the other. The executive branch’s broad reading, applied without a verifiable factual predicate for the specific operation at issue, risks producing a system where Article II (the president’s powers) swallows Article I (Congress’s powers) entirely. That risk is not present in genuine emergencies, where the functional argument has real purchase. It arises in cases where the emergency itself is contested and the evidence for it is withheld from the branch the Constitution assigns the power to declare war.

Proposed Reforms and the Obstacles to Enacting Them

Legal scholars and reform-minded members of Congress have proposed several fixes. One option is to amend the War Powers Resolution to define “imminent threat” specifically, perhaps borrowing from the Caroline doctrine’s requirement that the threat be instant and overwhelming. Another is to create an expedited court review process for war powers disputes, one that moves quickly enough to matter before the military operation ends. This would give courts a defined role in judging whether the factual basis, the actual evidence, that justifies emergency action is met. A third proposal is to set up a congressional war powers board with subpoena power the executive branch could not legally ignore, to require the executive branch to produce threat evidence before military operations begin.

The Brennan Center’s research on emergency powers has documented how post-September 11 administrations redefined “imminent” from the traditional international law meaning (an attack that is about to happen) to something closer to “there is a strategic threat that may appear at an unspecified future point.” In plain terms: “imminent” used to mean the attack is coming right now. After 9/11, administrations began using it to mean the threat exists somewhere in the future. That shift in definition is not a dispute over words. It is the mechanism by which the legal standard for unilateral presidential war-making has grown from genuine emergencies to something approaching presidential discretion.

None of these reform proposals have gained enough political support to be enacted. And even if they were, the Office of Legal Counsel would likely interpret any vague language as giving the president more power, not less. That is what OLC does, consistently, across administrations of both parties, for fifty years.

The deeper obstacle is that reforming war powers requires the political branches to agree to limit themselves. That requires a level of bipartisan unity that does not exist when one party controls the White House and the other does not. Senator Fetterman voted against the war powers resolution on Iran not because he agreed with the legal theory of executive power, but because he supported Trump’s decision to strike Iran as a policy matter. That kind of party-line voting makes a two-thirds veto override mathematically impossible before the operation even begins.

So the question that matters going forward is not whether Congress will pass a war powers resolution. It probably will not, at least not one that survives a veto. The question is whether the combination of the Rubio contradiction, the absence of evidence in the classified briefing, and the ongoing military operation will build enough political pressure to force a genuine AUMF debate. That would be a debate where Congress is required to vote on whether to authorize this specific war against Iran, with this specific evidence, under this specific legal theory. That debate has not happened yet. Whether it does will depend on how the conflict develops, how many more American soldiers are killed, and whether the public develops a lasting interest in the legal structure of a war being fought in its name.

The undefined “imminent threat” standard has survived Gulf of Tonkin, Iraq, Soleimani, and now Iran. Defenders of the current framework argue that this staying power reflects genuine democratic legitimacy — that a standard with bipartisan executive support and congressional acquiescence across a dozen administrations represents a workable constitutional balance rather than a failure of design. Critics contend that it has survived because closing the gap requires something the American political system has not produced in fifty years: a Congress willing to fight for its own war-making authority against a president of the opposing party, and a judiciary willing to say that some presidential decisions are reviewable even when they involve national security. Until one of those things changes, the pattern will continue. Military action will proceed. Threat assessments will remain classified. Congress will vote on resolutions that fail. And the executive branch will report, accurately, that it has complied with the law.

Our articles make government information more accessible. Please consult a qualified professional for financial, legal, or health advice specific to your circumstances.

Follow:
Our articles are created and edited using a mix of AI and human review. Learn more about our article development and editing process.We appreciate feedback from readers like you. If you want to suggest new topics or if you spot something that needs fixing, please contact us.