Houthis Say They Struck Aramco Sites at Jizan and Yanbu; Fire Reported at Jizan Refinery

Fire at Jizan, a Claim of Dozens of Missiles, and No Official Damage Count

Early on Saturday, July 25, 2026, Yemen's Houthi movement said it had struck two Saudi Aramco sites on the Red Sea coast. Houthi military spokesman Yahya Saree said his forces fired ballistic missiles, cruise missiles and drones at facilities in Jizan and Yanbu^[1][2]. A fire broke out at the Jizan refinery complex, and NASA's satellite fire-tracking service, FIRMS, recorded an abnormal heat spike there at about 01:17 UTC^[3][17]. Saudi air defenses said they intercepted missiles aimed at the Yanbu oil installations^[4].

Jizan is not a minor site. It processes about 400,000 barrels of crude a day and ranks as Saudi Arabia's fifth-largest refinery^[3]. It was the first Houthi attack on Saudi oil infrastructure since 2022^[2]. Saree described the targets as "sensitive Aramco-affiliated facilities" and claimed dozens of missiles and drones were involved — a claim that is, for now, the most detailed account of the attack that exists^[1].

What is missing is just as notable. Aramco and the Saudi government had issued no damage assessment and no casualty count by the weekend^[2]. Gulf News reported that Saudi state media, citing an energy ministry source, said refinery output dropped temporarily and would be covered from stockpiles^[11]. That is an official account, not an independent inspection, and it is the only word on the actual damage so far.

The $100 Number Everyone Is Repeating Belongs to a Different Attack

Here is a detail that got lost in a lot of the coverage. Brent crude, the global oil benchmark, closed above $100 a barrel on July 23 — two full days before the Jizan and Yanbu strikes^[5]. That was its first close above $100 since May 26, and it happened after the Houthis attacked two Saudi tankers, the Encelia and the Layla, on July 22, not after any refinery was hit^[5][7].

So the refinery fire didn't cause the $100 oil. It landed on top of a price that had already moved. The distinction matters because it changes what the attack actually did: it added fuel to a rally already running, rather than lighting the match itself^[1][5].

That gap between the trigger and the price is itself a clue to how oil markets work. Traders aren't pricing today's barrels — they're pricing what they expect to happen to tomorrow's supply. When the risk of a future disruption rises, prices rise immediately, even if no oil has actually stopped flowing yet. Analysts at Goldman Sachs have estimated that roughly $14 of every Brent barrel right now is this kind of risk premium, not the cost of anything physically lost^[14]. It's why a ceasefire could pull money out of the price faster than any repair crew could fix a pipeline.

Why the Fighting Keeps Landing on the Same Stretch of Coast

There's a reason both sides keep aiming at this particular part of Saudi Arabia, and it has to do with plumbing. Most Gulf oil normally leaves through the Strait of Hormuz. With Hormuz effectively shut in the wider U.S.-Iran war, Saudi Arabia has been pumping crude the other direction instead — west across the country through the East-West pipeline, known as Petroline, to the Red Sea port of Yanbu^[12][13].

Riyadh pushed that pipeline to a record of about 7 million barrels a day in March 2026, and roughly 5 million barrels a day of Saudi exports now leave through Yanbu alone^[12][13]. Before the wider war, the U.S. Energy Information Administration estimated total bypass capacity around Hormuz — this pipeline plus the UAE's Fujairah port — at only about 3.5 million to 5.5 million barrels a day^[13]. Much of that slack is now already in use.

That's the trap. The pipeline that let Saudi Arabia dodge trouble in the Strait of Hormuz put its main remaining export route within range of Houthi drones and missiles. For Riyadh and its customers, Yanbu is the exit that's still open. For the Houthis, it's the one soft spot on a coastline they can already reach cheaply^[6][7].

The asymmetry cuts against whoever has to defend it. A missile attacker needs only a few weapons to get through; a defender has to stop nearly all of them, at every site, every time. That played out this week exactly as the math predicts: missiles aimed at Yanbu were reported intercepted, while a fire burned at Jizan^[3][4]. Reporting also indicates that one of the Patriot missile batteries covering Saudi territory is operated by Greek forces under an agreement with Riyadh — a sign of just how thin the coverage is stretched across the kingdom's energy sites^[3].

Each Side Tells the Story From a Different Starting Point

Ask the Houthis when this began and they don't start with Saturday's missiles. They start with what they call years of Saudi restrictions on the ports and airports they control, and with Saudi airstrikes on Hodeidah and Kamaran Island roughly a day before the Aramco attack^[1][8]. In their telling, hitting Aramco is deterrence — raising the cost of the next Saudi raid — and a matter of symmetry, since they'd declared their own naval blockade of Saudi Arabia on July 20^[6].

Ask Saudi Arabia and the timeline runs the other way. Riyadh points to a Houthi attack on a Saudi airport on July 13, the blockade declaration on July 20, and the tanker attacks on July 22 — all before its own strikes on Hodeidah^[6][7][8]. Its case is that it held a truce for four years and stopped fighting, and the Houthis broke it. Saudi officials also argue the Hodeidah strikes were deliberately narrow, aimed at military capability and not at the port itself, since that port is the main route for food and fuel into northern Yemen^[8].

Washington has its own frame, layered on top of both. President Trump has said the United States will hold Iran responsible for further Houthi attacks on Red Sea shipping, on the reasoning that the missiles and drones are Iranian-designed and that Tehran's backing is what makes the campaign possible^[2][9]. Iran denies directing Houthi operations, says Yemen makes its own military decisions, and argues that it is the party under attack — noting that U.S. strikes on Iran had run for 12 consecutive days before the first quiet night around July 25^[2][9].

A fifth group, spanning restraint-minded voices on both the American right and left along with humanitarian organizations, reads the whole sequence as an escalation trap: a collapsed U.S.-Iran deal, then a blockade, then tanker attacks, then Hodeidah, then Jizan, each step feeding the next within days^[1][2][6][8]. They argue a war spanning Iran, Yemen and the Red Sea has never had a vote in Congress, and that years of Saudi and coalition bombing never disarmed the Houthis in the first place — evidence, they say, that more bombing won't now either^[16].

For American Drivers, the Fight Arrives at the Pump

Whatever the strategic argument, there's a number that reaches ordinary Americans faster than any of it. AAA put the national average price for regular gasoline at $4.09 a gallon on July 23, up 15 cents in just a week^[10]. Crude oil is the biggest single ingredient in that price, so a fire at a Saudi refinery or a blockade in the Red Sea shows up at U.S. gas stations within weeks, not months.

That link is why gasoline is doing double duty in the debate. Supporters of the administration's approach point to it as proof the Houthi attacks are a direct tax on American drivers, one that justifies pressuring Iran further up the supply chain^[9][10]. Critics of an expanding war point to the same $4.09 figure as proof the campaign itself is what's raising prices, regardless of who fired the first shot^[10][18]. Both sides are reading the identical number as evidence for opposite conclusions.

For Saudi Arabia, the exposure runs deeper than one refinery fire. The kingdom's economic plan, known as Vision 2030, is meant to diversify the economy away from oil — but it's funded by oil revenue and depends on investors believing the country is stable^[2]. A prolonged conflict means higher borrowing costs and delayed projects, on top of whatever output Jizan actually lost^[2].

What Coverage Diverges On, and What Nobody Can Confirm Yet

Where different outlets started the story tracked closely with where their audiences and governments sit. Al Jazeera, funded by Qatar, opened its account with the Saudi strikes on Hodeidah and Kamaran Island the day before, establishing the Houthi attack as retaliation before describing it^[1]. Gulf News and The National, both UAE outlets, led instead with the Saudi state account of a temporary output drop, framing the story from inside official Saudi and Emirati channels rather than including the Houthi rationale^[11][16].

American coverage split in a familiar way. Fox News and The Washington Times both led with "Iran-backed" ahead of any detail about the specific attack, assigning agency to Tehran before the reporting got to the Houthis themselves^[9][15]. The Washington Post used the word "claim" for the Houthi announcement, accurate given the lack of an Aramco damage report, but framed the broader story as the Iran war "widening," which places U.S. policy upstream of the Houthi decision to strike^[2]. Reuters' "exchange fire" headline aimed for neutrality but arguably went too far the other way, flattening a dated sequence of blockade, tanker attacks, airstrikes and missiles into what reads like a mutual scuffle with no starting point^[4].

The most important gap in the story is also the simplest one: nobody outside Aramco and the Saudi government actually knows how much oil capacity was lost. Every number in circulation — a fire, a heat signature, a claim of dozens of missiles, an official statement about stockpiles covering the shortfall — is either a claim from a combatant or an estimate from outside sensors^{[1][2][3][11]}. An independent damage assessment, if one comes, will be the first hard data point in a story that has so far run almost entirely on competing statements.