House Votes 215-208 to End the Iran War

For the first time in three months of active combat, a majority of the House of Representatives voted Wednesday to reassert Congress's constitutional authority over the war with Iran. The vote was 215 to 208. Four Republicans crossed the aisle. Cheers erupted on the House floor. And the war continues.

By Alena Harrison | Armed Forces News | June 3, 2026

The Vote That Just Changed the Political Calculus on the Iran War

At some point Wednesday afternoon, the numbers stopped working for Speaker Mike Johnson.

For more than three months — since President Donald Trump launched Operation Epic Fury against Iran on February 28, 2026, without a congressional declaration of war or an Authorization for Use of Military Force — Johnson had managed to hold enough of his Republican conference together to block every attempt to invoke the War Powers Resolution of 1973. The first attempt failed 212-219 in March. The second failed. The third failed. Each time, the margin narrowed. Each time, the toll of a war that has driven up gas prices, killed American service members, destabilized the Persian Gulf, and stretched U.S. forces across an active combat theater grew harder to defend back home.

On May 21, with the fourth vote imminent and absences threatening the outcome, Johnson abruptly sent the House home for Memorial Day recess rather than let the floor vote proceed. It was a delay, not a solution.

On Wednesday, June 3, 2026, the fourth war powers vote finally happened. The resolution passed 215-208.

Cheers erupted in the House chamber.

It was the first time since the start of the Iran war that either chamber of Congress had passed a measure to end it.

What the Resolution Actually Does — and Doesn't Do

Before examining the politics, the history, and the stakes for the service members and veterans who bear the direct cost of this war, it is essential to be precise about what the House just passed — and what it did not.

The resolution passed Wednesday is a concurrent resolution. It directs President Trump to remove U.S. Armed Forces from unauthorized hostilities against Iran within a specified period unless Congress passes a formal declaration of war or an AUMF. It was introduced by Rep. Gregory Meeks of New York, the top Democrat on the House Foreign Affairs Committee.

A concurrent resolution does not require the president's signature. Democrats argue this means it is legally binding if passed by both chambers under the War Powers Resolution's own framework — specifically Section 5(c), which provides that Congress may direct the removal of forces at any time by concurrent resolution.

Republicans dispute this interpretation. The Trump administration has argued that the War Powers Resolution itself is an unconstitutional infringement on presidential commander-in-chief authority — a position no administration, Democratic or Republican, has ever fully conceded. In a formal Statement of Administrative Policy opposing the Meeks resolution, the White House argued that the question was moot in any event: "There are no present hostilities from which to remove U.S. Armed Forces. The hostilities that began on February 28, 2026, have terminated with the ceasefire ordered by the President on April 7, 2026."

The problem with that argument, as critics note, is that U.S. forces have continued to conduct strikes in Iran and against Iranian-linked targets since the April 7 ceasefire — including strikes on Qeshm Island as recently as this week, which triggered an Iranian drone attack on Kuwait International Airport that killed at least one person and wounded more than 60.

The resolution now heads to the Senate, where its path is uncertain. Senate Democrats have been inching closer to the 51 votes they need, including winning a procedural vote last month with help from a handful of Republicans. A final Senate vote has not yet been scheduled.

Even if the Senate passes its own version — and both chambers reconcile them — Trump would almost certainly contest the resolution's legal authority, and an override of a presidential veto would require two-thirds support in both chambers, a threshold that appears nowhere near achievable in the current Congress.

The bottom line: Wednesday's vote is legally significant, historically significant, and largely symbolic in its immediate operational effect. The war will continue. But the politics of the war just changed.

A Constitutional Framework — and Its Limits

To understand why this vote matters beyond its symbolic weight, it helps to understand the law at the center of the dispute.

The War Powers Resolution was enacted on November 7, 1973, over the veto of President Richard Nixon, at the tail end of the Vietnam War. Congress had watched a conflict drag on for years and cost tens of thousands of American lives without ever formally declaring war, and it passed the resolution to ensure it would never again be cut out of decisions about committing American forces to sustained combat.

The law requires the president to notify Congress within 48 hours of committing armed forces to military action. It prohibits forces from remaining engaged for more than 60 days — with a further 30-day withdrawal period — without a congressional declaration of war or a specific statutory authorization. It also provides, in Section 5(c), the concurrent resolution mechanism that Democrats invoked Wednesday.

Every president since Nixon has contested the resolution's constitutionality while nominally complying with its reporting requirements. Every president has submitted war powers reports "consistent with" rather than "pursuant to" the resolution — a deliberate phrasing designed to preserve the executive's position that the law does not constitutionally bind the commander-in-chief.

The Iran war crossed the 60-day clock threshold weeks ago. The ceasefire the White House declared on April 7 has not stopped active U.S. military strikes. And Trump, like his predecessors, has not sought congressional authorization.

As Sen. John Curtis, a Republican from Utah who has written publicly about the war powers framework, argued in a recent op-ed: "The War Powers Resolution was born out of the hard lessons of Vietnam. In 1950, 35 advisers were sent to assist the French in training Vietnamese troops. By 1954, the French had withdrawn, and the American president had authorized 3,200 on-the-ground advisers. Fifteen years later, there was still no congressional declaration of war, but America had, at its peak, more than half a million American soldiers on the ground — at an eventual cost of almost 60,000 American lives."

Curtis's point, made by a Republican, frames the constitutional stakes plainly: the 60-day limit exists precisely to prevent a conflict that begins as something limited from becoming something that is not.

The Four Republicans Who Crossed the Aisle

Every Democrat voted yes. That alone was not enough. The resolution needed Republican votes to pass, and four members of the House GOP conference provided them.

Rep. Brian Fitzpatrick (R-PA) — A former FBI agent and one of the more moderate members of the Republican conference, Fitzpatrick has long been one of the few House Republicans who regularly breaks with leadership on national security and foreign policy when he believes the constitutional framework demands it.

Rep. Thomas Massie (R-KY) — A libertarian-leaning conservative and one of the earliest Republican critics of executive war-making power, Massie has been consistent on this issue across administrations. He voted for the first failed war powers resolution in March as well.

Rep. Warren Davidson (R-OH) — Davidson, also a consistent voice for congressional war authority, voted for the March resolution as well. His support for Wednesday's vote was not a surprise, but it remained politically significant given the pressure Republican members faced from Trump and House leadership.

Rep. Tom Barrett (R-MI) — Barrett was among the new Republican defectors Wednesday, joining the three who had voted yes before. His vote represents the expanding coalition of Republicans willing to put the constitutional question above party loyalty on this specific issue.

One notable change on the Democratic side: Rep. Jared Golden of Maine, who had voted against the three previous war powers resolutions, reversed course Wednesday and voted in favor. His flip gave Democrats unanimity on the measure for the first time — a sign of how the political dynamics around the war have shifted over three months.

What Johnson Said — and What His Members Heard

Speaker Johnson had tried to hold the line. On Wednesday, before the vote, he made his case directly.

"The president is now in the process of concluding a peace agreement, and we have to allow him the latitude to do that," Johnson said, according to reporting by MS NOW. He warned the resolution would have a "very negative" impact on negotiations and that it would "weaken us, our position, and our leverage in negotiation."

Rep. Brian Mast, the chairman of the House Foreign Affairs Committee, was blunter. "It's just a total BS vote," Mast told reporters, according to NBC News. "I think there's no Democrat, no Republican that can tell you what forces they would want pulled from Iran. There's really nothing they actually want pulled from there."

But the argument that the resolution would undermine negotiations was becoming harder to make convincingly. Peace talks have dragged for months without a conclusive agreement. The ceasefire ordered in April has been punctuated by continued strikes on both sides. This week alone, Iran struck Kuwait's airport with 13 ballistic missiles and 17 drones. Trump himself, on Wednesday, said a deal might happen "over the weekend" — the same optimistic timeline the administration has offered repeatedly without result.

Some Republicans, according to reporting by CNN, were also feeling direct pressure from constituents on the economic costs of the war — particularly rising energy prices driven by the partial closure of the Strait of Hormuz, through which roughly 20 percent of the world's oil normally flows.

Rep. Gregory Meeks, who introduced the resolution, had said openly in recent weeks that he believed Johnson was running out of room. "A lot of my Republican colleagues are feeling the pressure back home when they're looking at the cost of food, the cost of gas," Meeks told CNN before the vote. "He's feeling heat. He's trying to cover for the president. But I think the time of him being able to cover for the president is rapidly ending."

On Wednesday, that assessment proved correct.

What Democrats Said

House Minority Leader Hakeem Jeffries, joined by his top two deputies Katherine Clark of Massachusetts and Pete Aguilar of California, issued a statement immediately after the vote.

"Following repeated attempts to get sycophants in the Republican-controlled House to join us, House Democrats successfully passed our War Powers Resolution today to stand up for the American people and hold Donald Trump accountable," the statement read, as reported by NPR. "It is now time for Senate Republicans to do the right thing."

Earlier in the week, Jeffries had framed the vote in starker terms. "This reckless and costly war of choice needs to end today," he said, according to PBS NewsHour.

The Vote History: How We Got Here

Wednesday's 215-208 passage was the fourth war powers vote on Iran since the conflict began. The trajectory of the vote tallies tells a story about the war's growing political toxicity.

Vote 1 — March 5, 2026: The first war powers resolution, introduced by Reps. Ro Khanna and Thomas Massie, failed 212-219. Only Massie and Davidson crossed party lines. Four Democrats — Reps. Henry Cuellar of Texas, Jared Golden of Maine, Greg Landsman of Ohio, and Juan Vargas of California — voted no.

Vote 2 and Vote 3: Subsequent attempts also failed, but with incrementally more Republican support and incremental movement among Democrats.

May 21, 2026: With the fourth vote on the verge of passing due to Republican absences, Johnson pulled it from the floor and sent members home early for Memorial Day recess. The delay bought time but didn't change the underlying math.

June 3, 2026 — Vote 4: The resolution passes 215-208. Four Republicans vote yes. Every Democrat votes yes for the first time.

The progression from 212-219 in March to 215-208 in June reflects a war that is becoming harder to defend politically with every week it continues without a clear resolution.

What It Means for Service Members and Veterans

The war powers debate is an abstraction in Washington. For the men and women deployed to the Persian Gulf and the broader Middle East theater, it is anything but.

More than 90 days into active combat operations, U.S. service members are operating in a conflict that has never received formal congressional authorization. They are fighting under rules of engagement developed without the input or oversight of the legislative branch. They are subject to a ceasefire that their own government has acknowledged is being violated by both sides.

The 60-day clock embedded in the War Powers Resolution exists for a reason that should resonate with anyone who has served: it was designed to ensure that no American in uniform could be committed to sustained combat for longer than two months without the explicit backing of the nation's elected representatives. That limit has been exceeded. The authorization has not been granted.

For veterans, the policy stakes are also real. Wars without clear authorization tend to end without clear plans. Wars without clear plans tend to produce veterans without clear paths to the benefits and care they were promised. The pattern from Vietnam to Iraq to Afghanistan is familiar: the political difficulty of ending a conflict shapes what that conflict's veterans receive when it is over.

Wednesday's vote does not end the Iran war. It does not immediately change anything on the ground. But it changes the political landscape in which decisions about the war will be made — and it puts every Republican senator on record for a vote that is coming, whether leadership wants it or not.

What Comes Next

The resolution now goes to the Senate. Senate Majority Leader Mitch McConnell and Republican leadership have resisted scheduling a war powers vote, but Democrats have been using procedural tools to force action.

Last month, the Senate advanced its own war powers measure on a procedural vote after Sen. Bill Cassidy of Louisiana — who had previously voted no — flipped to yes just days after Trump had backed his opponent in Louisiana's Republican primary. Cassidy's defection changed the political math and is widely seen as the moment Senate passage became a real possibility rather than a distant one.

A final Senate vote has not been scheduled as of publication.

If the Senate passes a compatible resolution, questions about whether it carries the force of law without a presidential signature will likely move into the courts. The Trump administration has already signaled it will contest the resolution's authority. Legal scholars are divided on whether a concurrent resolution under Section 5(c) of the War Powers Resolution is enforceable without the president's signature, particularly after a 1983 Supreme Court ruling that complicated the use of legislative vetoes.

What is not in doubt: the political pressure on the administration to produce a durable peace agreement — or to seek formal congressional authorization — has grown significantly tonight. The House has now spoken. The Senate is moving. And the Strait of Hormuz remains largely closed.

Sources and Attribution

All quotes in this article are sourced to named individuals and verified through multiple published reports. All vote tallies are sourced to official congressional records and contemporaneous reporting.

Sources consulted:

• Rep. Gregory Meeks (D-NY), resolution sponsor — statements and floor remarks, June 3, 2026, as reported by NBC News and CNN
• Speaker Mike Johnson (R-LA) — pre-vote statement, June 3, 2026, as reported by MS NOW and CNN: "The president is now in the process of concluding a peace agreement, and we have to allow him the latitude to do that"; "It weakens us, our position, and our leverage in negotiation on the peace in that situation"
• Rep. Brian Mast (R-FL), House Foreign Affairs Committee Chairman — statement to reporters, June 3, 2026, as reported by NBC News: "It's just a total BS vote"
• House Minority Leader Hakeem Jeffries (D-NY), Rep. Katherine Clark (D-MA), Rep. Pete Aguilar (D-CA) — joint statement, June 3, 2026, as reported by NPR: "Following repeated attempts to get sycophants in the Republican-controlled House to join us..."
• Hakeem Jeffries — earlier statement this week, as reported by PBS NewsHour: "This reckless and costly war of choice needs to end today"
• Vote tally, June 3, 2026: 215-208, confirmed by NBC News, CNN, NPR, CBS News, The Hill, MS NOW, and AP
• Republican yes votes confirmed: Reps. Thomas Massie (KY), Brian Fitzpatrick (PA), Tom Barrett (MI), Warren Davidson (OH) — confirmed by NBC News, CNN, The Hill, MS NOW
• Vote 1, March 5, 2026: Failed 212-219 — reported by TIME, ABC News, Al Jazeera
• White House Statement of Administrative Policy — opposing the Meeks resolution, citing April 7, 2026 ceasefire; reported by The Hill
• War Powers Resolution of 1973 — 50 U.S.C. 1541–1548; summary from GovTrack, Congress.gov, and HISTORY.com
• Sen. John Curtis (R-UT) op-ed — published on curtis.senate.gov, May 2026: "Lessons from our war powers past — 60 days must mean 60 days"
• Sen. Bill Cassidy (R-LA) procedural vote flip — reported by NPR, June 3, 2026
• Iran strike on Kuwait International Airport, June 3, 2026 — 13 ballistic missiles, 17 drones; 1 killed, 60+ wounded — reported by ABC News, Al Jazeera, Euronews
• Strait of Hormuz crisis background — Wikipedia/2026 Strait of Hormuz crisis; House of Commons Library research briefing, updated June 2, 2026

Armed Forces News is an independent military news publication. We have no affiliation with any political party, the Department of Defense, or any party to the legislation described in this article. Read How Iran Strikes U.S. Bases and Iran's Nuclear Program after Operation Epic Fury.

Alena Harrison covers defense policy and congressional affairs for Armed Forces News. She is an 8 year veteran of the military.