Skip to content
Briefings are running a touch slower this week while we rebuild the foundations.See roadmap
European Tech Sovereignty
13APR

Lebanon clause hands Israel a deal veto

3 min read
17:09UTC

A clause ending the Israel-Hezbollah war in Lebanon entered the draft US-Iran accord, and Israeli Prime Minister Benjamin Netanyahu objected to it directly to Trump in a call on Sunday 24 May.

TechnologyDeveloping
Key takeaway

An Israel-Lebanon clause inside the US-Iran draft gives Netanyahu a veto over a deal he did not negotiate.

The draft memorandum of understanding (MOU) between Washington and Tehran now carries a clause ending the war between Israel and Hezbollah in Lebanon, and Israeli Prime Minister Benjamin Netanyahu objected to it directly in a phone call with Trump on Sunday 24 May 1. An Israeli official framed the concern bluntly: a Lebanon condition inside the Iran accord would oblige Israel to wind down its own campaign against Hezbollah, the Iran-backed militia it has fought across the Lebanese border.

That objection matters because of where it sits. Trump had declared the deal "largely negotiated" between the United States and Iran on 23 May , with the two principals close on the core terms. A clause that binds a third country's military campaign, inserted into a bilateral text, gives Netanyahu a lever over an agreement he is not formally party to. He need not reject the deal; he need only refuse to wind down in Lebanon, and the clause cannot be honoured.

The veto stacks on top of an existing wall. Tehran has tied any Hormuz reopening to the release of its frozen assets in Qatar first , while Trump has posted that the US blockade holds until a deal is "certified and signed" . Iran wants relief up front; Washington offers it only after performance. A Lebanon clause that depends on Israeli cooperation adds a second actor whose timing no one at the table controls.

The structure now requires three things to align that answer to three different authorities: a US Treasury order to free the Qatari assets, an Israeli decision to stand down in Lebanon, and a signed instrument neither Washington nor Tehran has yet produced. Each is a separate lock, and a deal that needs all three open at once is harder to close than one that needed only the two principals to agree.

Deep Analysis

In plain English

The US and Iran had been drafting a preliminary peace agreement (a "memorandum of understanding"). Hidden inside the draft was a clause requiring the war between Israel and Hezbollah, the Lebanese militia that Iran backs, to end as part of the deal. Israel's Prime Minister Benjamin Netanyahu called Donald Trump directly on 24 May to object. His concern: if the US-Iran deal requires Israel to stop fighting Hezbollah in Lebanon, Israel would effectively lose its ability to finish that campaign on its own terms. Netanyahu would have no choice but to wind down operations that his government says are essential to Israeli security. This gives Israel a practical veto over a clause in a deal between two other countries (the US and Iran). Trump has to decide whether to drop the Lebanon requirement from the deal, override Netanyahu's objection, or find a different arrangement.

What could happen next?
  • Risk

    If the Lebanon clause stays in the MOU, Netanyahu may publicly break with Trump over Iran, damaging the US-Israel relationship at a moment when the deal requires Israeli operational restraint.

    Immediate · Suggested
  • Consequence

    Iran's nuclear sequencing (Phase 1 Hormuz + assets, Phase 2 nuclear at 60 days) rests on the Lebanon clause providing Iranian leverage; removing it narrows what Iran gets from the deal and may cause Tehran to reopen closed issues (ID:3610).

    Short term · Assessed
  • Precedent

    Netanyahu's direct objection to Trump sets the precedent that Israel's approval is required for any US-brokered Middle East deal that touches Israeli military operations, a structural constraint on US diplomacy beyond this conflict.

    Long term · Assessed
First Reported In

Update #108 · US strikes Bandar Abbas as deal talk stalls

CNN· 26 May 2026
Read original
Different Perspectives
ASML / European tech industry
ASML / European tech industry
ASML's Q2 2026 guidance came in €300m below consensus as China DUV revenue collapsed 17 percentage points; the company's CEO wrote US export-control outcomes directly into 2026 guidance. European tech firms named on the USTR retaliation list alongside SAP, Siemens and Spotify face the same calculus: US trade exposure constrains what Brussels can legislate on their behalf.
France / Anne Le Henanff
France / Anne Le Henanff
Le Henanff chaired the G7 Digital Ministerial at Bercy on 29 May with CAIDA off the agenda, pivoting France's presidency to AI safety principles it had not designed the week around. France backs CAIDA but cannot override Berlin's tariff calculus, so the ministerial produced no new French-led commitment.
Germany / Federal government
Germany / Federal government
Berlin's automotive sector faces up to $200bn in threatened US tariffs, a commercial exposure that dwarfs any benefit CAIDA's public-sector cloud rules would deliver to German digital firms. Federal silence inside the College of Commissioners functions as a block under consensus adoption rules without requiring a formal veto.
USTR / Ambassador Andrew Puzder
USTR / Ambassador Andrew Puzder
Puzder's public warning on 25 May that CAIDA is inconsistent with the EU-US trade framework was the first time Washington made its bilateral pressure visible before a Commission adoption vote rather than after. The USTR Section 301 determination on 24 July provides the enforcement backstop.
European Commission / Henna Virkkunen
European Commission / Henna Virkkunen
Virkkunen framed the third slip as a procedural delay in finalising a 400-page text without addressing Puzder's trade-framework red line publicly. The Commission enforces existing law against Google while losing the legislative timeline on CAIDA, exposing an asymmetric position: enforcement holds; new sovereignty legislation does not.
OpenForum Europe / open-source community
OpenForum Europe / open-source community
The EUR 350m Sovereign Tech Fund has no Commission host, no budget line, and no commissioner's name attached six weeks after the April conference, while Germany is already paying maintainers to staff international standards bodies. The CRA open-source guidance resolves contributor liability but leaves the financial-donations grey area open with the 11 September reporting clock running.