Skip to content
You can now search across every topic, entity and event.What's new
Iran Conflict 2026
17JUN

Zelenskyy sacks Fedorov after army talks

2 min read
09:37UTC

Zelenskyy dismissed Defence Minister Mykhailo Fedorov on 15 July after a meeting with military leadership. Fedorov gave a different reason: a permanent conflict with Commander-in-Chief Oleksandr Syrskyi.

ConflictDeveloping
Key takeaway

Fedorov's exit removes the minister, not the mobilisation and brigade problems Zelenskyy blamed him for.

Volodymyr Zelenskyy dismissed Defence Minister Mykhailo Fedorov on 15 July, after a meeting with military leadership, saying problems on the battlefield, in brigades and with mobilisation had not been resolved 1. Kyiv Independent and Ukrainska Pravda had reported two days earlier, citing a senior official, that the president was considering it 2. Fedorov confirmed his removal to reporters on the record and gave a narrower account of the cause: a permanent conflict with Commander-in-Chief Oleksandr Syrskyi, who he said blocked ministry initiatives.

The dismissal sat inside a government-wide reshuffle Zelenskyy announced on 12 July, in which Prime Minister Yulia Svyrydenko submitted her resignation. Parliament voted on a new prime minister and cabinet on 16 July. Fedorov had run the ministry through a stretch in which the line of contact barely moved, with Russian forces losing men at seventeen times Ukraine's daily rate for ground that did not change hands . The battlefield problems Zelenskyy named were not problems a defence minister could fix alone, and the reshuffle around him suggests the president was reorganising a cabinet rather than isolating one failure.

Fedorov leaves with two entries on his ledger: persuading Elon Musk to keep Starlink out of Russian forces' hands, and the logistics lockdown campaign against Russian supply lines that he launched on 27 May. He declined the adviser role Zelenskyy offered him.

Deep Analysis

In plain English

Ukraine's government just lost its defence minister in the middle of the war. Mykhailo Fedorov, the civilian minister who ran weapons purchasing and day-to-day ministry business, was dismissed by President Zelenskyy on 15 July. Fedorov says the real reason was an unresolvable clash with Oleksandr Syrskyi, the general who commands Ukraine's troops in the field; Zelenskyy's public reasons were unresolved battlefield, brigade and mobilisation problems. A civilian minister and a battlefield commander can disagree over how the army recruits and organises troops without either side lying about it, and when that disagreement stays unresolved for months, one of the two usually has to go. Fedorov is a well-known figure who helped set up Ukraine's wartime digital government and pushed to deny Russian forces access to Elon Musk's Starlink internet service; he turned down a lesser advisory role rather than stay on.

Deep Analysis
Root Causes

Ukraine's Defence Ministry and General Staff share overlapping authority over mobilisation policy with no legally settled division of who sets brigade manning targets. The same ambiguity surfaced in Zaluzhny's removal in 2024 and has now resurfaced at ministerial level, with Fedorov naming the conflict directly rather than leaving it implied.

The timing compounds a reshuffle Zelenskyy had already queued rather than one driven solely by Fedorov: Prime Minister Yulia Svyrydenko had submitted her resignation on 12 July, three days before Fedorov's dismissal, with Parliament voting on a new cabinet on 16 July. Fedorov's exit landed inside a government-wide reset already in motion, which is part of why Zelenskyy could remove him without an immediate permanent replacement in hand.

What could happen next?
  • Meaning

    The dismissal makes public a command-authority dispute between Ukraine's civilian defence ministry and its military General Staff that had previously stayed behind closed doors.

  • Risk

    A ministry running without a confirmed minister during an active mobilisation crisis risks delayed decision-making on brigade manning and procurement until the Rada formally confirms a successor.

First Reported In

Update #24 · Fedorov sacked as the front stands still

RFE/RL· 19 Jul 2026
Read original
Different Perspectives
Lloyd's Market Association
Lloyd's Market Association
War-risk underwriters price the Houthis' Red Sea attacks because the group announces its targets in advance, but the unclaimed Damietta drone gives insurers a hit with no author to price against. An attack nobody claims costs shipping more than one that is claimed, since premiums are set against a known pattern, not raw damage.
US Central Command
US Central Command
CENTCOM has announced no strike on Iran since resuming bombing on 30 July within hours of an IRGC salvo on Jordan, and centcom.mil did not respond to requests to confirm any pause. The command has gone quiet before while a larger operation was being weighed, so silence alone proves nothing about what it has or has not done.
Hengaw
Hengaw
Hengaw recorded at least 67 executions in Iran during July, of which the state acknowledged only eight, and reported the 1 August execution of protest detainee Arvin Kheirkhahan at Shahrud with no advance notice to his family. A family's first notice of a death sentence is now usually the instruction to collect a body.
Egypt
Egypt
Egypt's government asked media on 2 August to report the Damietta attack accurately, named no author, and said no findings will be published before its own investigation concludes. Cairo holds the debris and jurisdiction over an attack on its own soil, and naming a culprit now would pull it into a dispute it has avoided for five months.
Iran's Foreign Ministry
Iran's Foreign Ministry
Araghchi called the Hormuz talks with Oman final-stage on 2 August, four days after his own deputy rejected Oman's lane proposal, and denied the Damietta drone strike as an Israeli false flag while two Iranian officials privately claimed it for Tehran. Iran's public position now contradicts itself on both files at once.
Bahrain and Kuwait
Bahrain and Kuwait
Bahraini and Kuwaiti aircraft flew their own strikes on Iranian depots in July with Emirati air cover behind them, and Ynetnews reports some Gulf capitals wanted the 2 August strike to proceed rather than stop. States that have already taken fire see a closing window on Iranian weakness, not a reason to pause.