Fetterman sides with GOP again on Iran war powers, and Democrats still can't stop him

 June 19, 2026 
Category: 

Sen. John Fetterman voted against his own party's war powers resolution for at least the second time in two months on June 16, handing Senate Democrats another defeat just one day before the United States and Iran signed a peace agreement. The Pennsylvania Democrat's defection helped sink Senate Joint Resolution 172, which failed 48-47 and would have called for removing U.S. forces from hostilities with Iran not authorized by Congress.

Five senators, Democrats Michael Bennet of Colorado, Cory Booker of New Jersey, and Bernie Sanders of Vermont, along with Republicans Josh Hawley of Missouri and Mitch McConnell of Kentucky, abstained entirely. Four Republicans broke ranks to vote in favor: Bill Cassidy of Louisiana, Susan Collins of Maine, Rand Paul of Kentucky, and Lisa Murkowski of Alaska.

None of that mattered. Fetterman's vote against the resolution was enough to deny Democrats the numbers they needed, continuing a pattern that has now stretched across multiple war powers attempts since the conflict with Iran began in late February.

A pattern Democrats cannot break

This was not a one-off. Fetterman cast a deciding vote against a similar measure in May, and that vote cost him a staffer who departed his office in protest. He has shown no sign of backing down.

The earlier confrontation in March was even more lopsided. AP News reported that the Senate voted 47-53 to defeat the first war powers resolution, with Fetterman joining 52 Republicans against his party's effort. Senate Democratic Leader Chuck Schumer framed the stakes in absolute terms before that vote: "Today every senator, every single one, will pick a side."

Fetterman picked a side. It was not Schumer's.

Sen. Tim Kaine, the Virginia Democrat who authored the original resolution, told the New York Post that senators who dodge war votes have no business sending troops into harm's way. "If you don't have the guts to vote Yes or No on a war vote, how dare you send our sons and daughters into war where they risk their lives?" Kaine said. That argument failed to move Fetterman then and has failed every time since.

By June, the margin had tightened. Just The News reported that one earlier attempt failed 49-50, with three Republicans crossing the aisle, making Fetterman's single defection the precise factor that killed the resolution. The June 16 vote was the closest yet at 48-47, but five abstentions and Fetterman's opposition kept the outcome the same.

Democrats have now tried and failed multiple times to reassert congressional authority over the Iran conflict. Each time, they have run into the same wall: a member of their own caucus who refuses to play along.

Fetterman's stated reasoning

Fetterman has not been shy about explaining himself. In an interview with NewsNation earlier this month, he was direct:

"My vote no is not a pro-war vote. It's absolutely a pro-no nuclear Iran."

In a Washington Post column published in May, he laid out his broader view. He called Iran "the leading state sponsor of terror" and wrote that it "should be held to account." He pointed to the conflict in Gaza as context for escalating threats from Iranian proxies.

"In the wake of the war in Gaza, Iran-backed Hamas and Hezbollah have ramped up their attempts to dismantle our ally."

He added: "I remained committed to fully backing the elimination of these terrorists and their leaders."

Fetterman has warned that Jewish voters face a bleak future inside the Democratic Party, and his stance on Iran fits squarely within that broader break from progressive orthodoxy on Israel and the Middle East.

On Fox News, Fetterman went further, calling the Iranian regime itself a decades-long atrocity. Fox News reported that he told the network: "If you want to talk about a war crime, you know, Iran is a 47-year-old war crime." He pledged to block future Democratic attempts to limit presidential war powers over the conflict, saying: "I will vote against that, because we have to stand by our military and allow them to accomplish the goals of Epic Fury."

That is not the language of a reluctant dissenter. That is a senator who has chosen a position and intends to hold it regardless of party pressure.

The conflict behind the vote

The war powers debate did not emerge from a vacuum. On February 28, 2026, the United States and Israel launched Operation Epic Fury, joint airstrikes targeting Iranian military and government sites. Iran's supreme leader was killed in the operation. Hezbollah entered the conflict days later, on March 2.

By late May, the human cost was mounting. Israeli forces announced that 24 troops had been killed in the war with Hezbollah as of May 28. A 20-year-old Israeli soldier, Sgt. Rotem Yanai, was killed by a Hezbollah drone launched from Lebanon on May 27. Israeli strikes in southern Lebanon on May 28 killed at least 12 people, including two children, and wounded 21 others.

Ceasefires came and went. A 10-day truce between Lebanon and Israel took effect around April 21, and Pakistan's prime minister publicly thanked President Trump for extending a separate ceasefire with Iran. Talks between Israel and Lebanon were scheduled in Washington for April 23.

Through all of it, Democrats pushed to reassert congressional control over the military campaign. And through all of it, Fetterman stood in their way, a pattern that has become one of the defining features of the Senate's handling of the Iran conflict.

Trump's position and the intelligence debate

President Trump told CBS News in March that Iran's "missiles are down to a scatter" and that the country had "nothing left in a military sense." The New York Times subsequently reported that military intelligence agencies assessed Iran still retains military capabilities, a tension between the White House's public framing and the intelligence community's findings that remains unresolved.

Fetterman's votes effectively preserved the president's authority to direct the campaign without new congressional restrictions. Whether one views that as responsible wartime deference or a dangerous abdication of legislative power depends entirely on one's priors. But the practical effect is clear: Trump's ability to order operations against Iran remains unchanged.

The peace agreement signed on June 17, one day after the Senate vote, calls for an immediate end to hostilities on all fronts and sets expectations for a new round of talks addressing Iran's nuclear program, among other issues. The timing raises an obvious question: did the resolution's failure clear the path for a deal, or was the deal coming regardless?

That question has no definitive answer yet. But Fetterman's allies can point to the sequence of events and argue that preserving presidential flexibility produced a result that congressional micromanagement might not have.

A Democrat who keeps breaking ranks

Fetterman's Iran votes are part of a larger pattern. He has repeatedly broken with Democrats on Fox News, gone after members of his own party in public, and positioned himself as a senator willing to stand alone when he believes the party line is wrong.

Senate Democrats have struggled to hold their caucus together on other high-profile votes as well. The same dynamic, a narrow margin undone by internal defections, has played out on issues beyond foreign policy, including Trump's Fed chair pick, where Schumer faced a bipartisan setback.

Sen. Andy Kim of New Jersey captured his party's frustration after the March vote, saying: "Senate Republicans once again failed to hold Trump accountable. Today's vote sends us down a dangerous path into a potentially endless war." But the uncomfortable truth for Kim and his colleagues is that it was not Republicans who failed them on the margin. It was Fetterman.

Democrats have pledged to try again. Fox News reported that Senate Democrats plan to launch yet another attempt to limit Trump's war powers when the chamber returns, and Fetterman has already promised to block it.

What remains unanswered

Several questions hang over the story. The exact terms of the June 17 peace agreement remain unclear beyond the broad outline of an immediate cessation of hostilities and a framework for future nuclear talks. Who now leads Iran's government, described only as operating "under new leadership" after Operation Epic Fury, has not been specified. And the identity of the staffer who left Fetterman's office after the May vote has not been publicly reported.

The intelligence community's assessment of Iran's remaining military capabilities, reported by the New York Times, has not been reconciled with the president's March statements. Whether the peace deal holds, and whether the next round of talks produces anything concrete on Iran's nuclear program, will determine how history judges both the military campaign and the senators who enabled or opposed it.

For now, the political reality is simple. Democrats cannot pass a war powers resolution as long as Fetterman votes no. They have tried at least four times. They have lost every time. And the senator from Pennsylvania has given every indication he will keep doing exactly what he has been doing.

When a party loses the same fight by the same margin because the same member of its own caucus keeps voting the other way, the problem is not the vote count. It is the party's inability to make its own case to its own people.

About Benjamin Clark

The Editors have spent decades in political analysis, bringing their expertise to Capitalism Institute. To learn more, read our About Us page.
A Project of Connell Media.
magnifier