TLP:CLEAR · Disclosure is not limited.

Red Sea Shipping Disruption: Threat Persists, No New Bab el-Mandeb Attack Established

Time window: Last 7 days · Audience: General analyst · Type: Situation report · DTG: 2026-11-03 01:10Z · Overall confidence: MEDIUM

BLUF

Commercial shipping through Bab el-Mandeb remains exposed to Houthi coercion, but this reporting does not establish a closure or a new attack on a vessel transiting the strait. The reported vessel attacks are centred on the Strait of Hormuz, the Persian Gulf and waters off Oman, while fighting in western Yemen is driving acute humanitarian pressure.

Executive summary

The reporting for 27 October to 3 November adds detail on fighting and civilian hardship in western Yemen, but no verified attack on a ship transiting Bab el-Mandeb. A local-media report citing the International Organization for Migration (IOM) says more than 300,000 people were displaced in Yemen over the preceding two months and estimates $45 million in aid needs over six months. The same report attributes 417 shells and 53 violations in two days in Taiz to the Yemen Rights and Freedoms Network; these incident figures lack independent corroboration in the supplied reporting. Separately, trade-publication reports describe attacks on tankers and an LNG carrier around Hormuz, the Persian Gulf and Oman. Conflicting details about the AL MAYEDA and RITI incidents limit confidence in their precise locations and dates. Reports of Houthi gains near the Bab el-Mandeb approaches also do not establish current control of Mokha or Dhubab.

Change from previous assessment

Since the 2 November prior brief, this assessment adds IOM-attributed reporting of more than 300,000 displacements over two months, a six-month aid requirement of $45 million, and reports of intense shelling and violations in Taiz. It also separates the reported attacks around Hormuz, the Persian Gulf and Oman from the Bab el-Mandeb threat picture. The new reporting does not establish a Bab el-Mandeb closure or a new attack on a transiting vessel, so the prior assessment of continued exposure without an established closure remains. Uncertainty over Houthi control of Mokha and Dhubab also remains.

Key judgments

1. Commercial traffic through Bab el-Mandeb is likely to remain exposed to Houthi coercion, particularly vessels linked to Saudi Arabia, over the next 0-14 days, but the reporting reviewed does not establish a new Houthi attack on a ship transiting the strait or a closure. The judgement rests on reporting of a Houthi campaign against international shipping and a declared blockade targeting Saudi-linked shipping, rather than on a verified incident in the current reporting period. Confidence is low because the supporting accounts are historical or undated and the current reporting contains no verified Bab el-Mandeb incident. (Confidence: low · ASSESSED)
   • I&W: A UKMTO warning identifies a vessel and coordinates for an attack in Bab el-Mandeb or the southern Red Sea. (0-14 days)
   • I&W: A Houthi announcement suspends attacks on commercial or Saudi-linked vessels and is followed by 14 days of verified commercial transits without a reported incident. (0-14 days)
2. Humanitarian pressure in western Yemen is likely to remain acute over the next 1-3 months. A local-media report citing IOM puts displacement above 300,000 people over two months and estimates $45 million in aid needs over six months; a separate NGO report says more than 800,000 people were cut off from assistance after the Taiz-Aden road was severed in early October. The same local-media account attributes 417 shells and 53 violations in two days in Taiz to the Yemen Rights and Freedoms Network, but those figures are not independently corroborated in the supplied reporting. Confidence is medium: the humanitarian picture has IOM attribution and separate NGO reporting on access constraints, while the current displacement and shelling details rely on limited reporting. (Confidence: medium · ASSESSED)
   • I&W: An IOM update reports continued new displacement or restricted aid access in Taiz or nearby western Yemen. (0-30 days)
   • I&W: IOM or another humanitarian organisation reports the Taiz-Aden road reopened, aid access restored and new displacement falling. (1-3 months)
3. The vessel attacks described in this reporting set are in or near the Strait of Hormuz, the Persian Gulf and Oman, not Bab el-Mandeb; they do not establish a new Red Sea attack or Houthi responsibility. Reports place the AL MAYEDA incident south of Lavan Island or near Hormuz, and give conflicting dates for the RITI incident, 29 or 31 October. Confidence is medium because the accounts are concentrated in trade-publication reporting and contain unresolved location and date discrepancies. (Confidence: medium · REPORTED)
   • I&W: UKMTO or flag-state reporting confirms the AL MAYEDA and RITI incident positions near Lavan Island, Hormuz or Khasab. (0-14 days)
   • I&W: A verified incident notice places an attack on a vessel within Bab el-Mandeb or the southern Red Sea during the reporting period. (0-14 days)
4. Current control of Mokha and Dhubab is not established. Reports say the Houthis captured both locations and seized other territory along Yemen's western coast; separate reporting describes a Saudi-led counteroffensive but does not confirm the recapture of either location. Confidence is low because the claims do not provide current, independently verified positions. (Confidence: low · ASSESSED)
   • I&W: Independently geolocated imagery or reporting identifies Houthi positions or administration in Mokha and Dhubab. (0-30 days)
   • I&W: The Yemeni government or coalition reports recapture of Mokha or Dhubab with independently geolocated evidence. (0-30 days)

Outlook & scenarios

Continued threat without a confirmed Bab el-Mandeb closure (55%)

Houthi pressure on Saudi-linked shipping and fighting along Yemen's western coast persist, while commercial operators manage exposure through selective routing decisions. No verified attack or formal closure at Bab el-Mandeb is established in the reporting.

Reduced threat and gradual return to routine transits (30%)

If fighting on Yemen's western front eases and no new shipping incident is reported, commercial operators begin reassessing diversions. The current reporting provides no evidence of a formal de-escalation, so this scenario depends on a change in battlefield behaviour.

Low-probability, high-impact disruption at Bab el-Mandeb (15%)

A Houthi attack on a commercial vessel or an attempt to enforce the declared blockade against Saudi-linked shipping prompts operators to suspend transits through Bab el-Mandeb. A subsequent military response expands the disruption beyond the immediate incident area.

Recommendations

1. Maintain separate incident logs for Bab el-Mandeb and the southern Red Sea, and for Hormuz, the Persian Gulf and waters off Oman. Record vessel identity, time, coordinates, reporting source and attribution before drawing regional conclusions.
2. Check UKMTO warnings, flag-state notices, ship-tracking data and operator route advisories daily for the next 14 days. Distinguish a verified Bab el-Mandeb incident from reported attacks elsewhere in the Gulf.
3. Seek authoritative confirmation of the AL MAYEDA location and the RITI incident date before using either event to assess maritime threat geography or actor responsibility.
4. Track IOM updates on displacement, aid needs and access in Taiz, alongside reporting on the Taiz-Aden road. Preserve the source and timeframe for each figure when updating humanitarian assessments.

Confidence & uncertainty

Overall confidence is medium. The humanitarian reporting includes IOM-attributed figures and separate NGO reporting on aid access, while the maritime incident accounts provide vessel names and locations but rely heavily on trade-publication reporting. Conflicting dates and locations for the AL MAYEDA and RITI incidents, limited independent confirmation of current fighting claims, and the absence of a verified Bab el-Mandeb incident constrain confidence in the current shipping picture.

Intelligence gaps

• [EEI 1.1 · PARTIAL] Incidents of hostile action against commercial vessels: vessel name/IMO, position (lat/long), time/date, observable damage or casualties, and weapon type reported (missile, drone, small-arms, explosive-laden boat). Recommended collection: maritime/AIS
• [EEI 1.2 · PARTIAL] Public Houthi claims of attacks or warnings tied to specific dates/routes, including social-media posts, official statements, and timing relative to merchant transits. Recommended collection: open-source/social_media
• [EEI 1.3 · PARTIAL] Unusual Houthi force posture indicators along Yemen’s Red Sea coast: movement or concentration of small boats, visible coastal missile/rocket emplacements, or logistics buildup at known launch sites (locations, timestamps). Recommended collection: imagery/satellite
• [EEI 1.4 · UNCOVERED] Intercepts or communications indicating orders, targeting lists, or intent to strike merchant shipping (messages referencing specific vessel classes, companies, or chokepoints). Recommended collection: signals/communications
• [EEI 2.1 · UNCOVERED] Reports or visual confirmation of floating or moored mines and debris fields in shipping lanes or approaches to Bab-el-Mandeb, with geolocation and time. Recommended collection: imagery/satellite
• [EEI 2.2 · UNCOVERED] Detection of mine-laying activity: small vessels loitering in lane approaches, unexpected AIS track patterns consistent with mine deployment, or salvage/mining vessels operating in the area. Recommended collection: maritime/AIS
• [EEI 2.3 · UNCOVERED] Hydrographic notices, naval warnings, or port authority advisories closing lanes or imposing route restrictions (text of Notice to Mariners, issuing agency, effective times/areas). Recommended collection: naval/port_authority
• [EEI 2.4 · UNCOVERED] Naval or commercial reports of mine-countermeasure operations or confirmed mine removal events (location, time, platforms involved). Recommended collection: naval/intelligence
• [EEI 3.1 · PARTIAL] Movements and presence of foreign warships and support vessels: names/classes, task group compositions, patrol areas and timelines, and whether vessels are conducting escort or interdiction operations. Recommended collection: naval/intelligence
• [EEI 3.2 · PARTIAL] Official announcements or directives from states/coalitions regarding convoys, armed escorts, protected corridor establishment, or changes to rules of engagement for merchant protection. Recommended collection: diplomatic/public_affairs
• [EEI 3.3 · UNCOVERED] Recorded interactions between naval forces and vessels in the corridor (hailings, boardings, warnings, defensive strikes), including timestamps and outcomes. Recommended collection: maritime/AIS
• [EEI 3.4 · UNCOVERED] Planned or ongoing multinational exercises, air ISR sorties, or logistics moves that increase or decrease naval capacity in the area (exercise name, participating units, dates, locations). Recommended collection: open-source/military_reporting
• [EEI 4.1 · PARTIAL] Transit volume and pattern changes: number of commercial transits per day/week through Bab-el-Mandeb and southern Red Sea compared with baseline, and instances of rerouting around Africa (position/time data). Recommended collection: maritime/AIS
• [EEI 4.2 · UNCOVERED] War-risk and hull insurance coverage changes: issuance refusals, premium increases for Red Sea transits, or explicit route exclusions by underwriters (policy notices or market rate data with dates). Recommended collection: commercial/insurance_data
• [EEI 4.3 · UNCOVERED] Freight and charter market signals tied to the corridor: spot rates for container, tanker, and dry bulk routes affected by Red Sea disruptions, and reported port congestion or turnaround-time increases at nearby hubs. Recommended collection: commercial/market_data
• [EEI 4.4 · PARTIAL] Incidents of cargo denial or diversion for critical goods (crude oil, refined products, LNG, high-value container cargo) including vessel IDs, cargo type, reroute/turnback actions, and economic impact estimates where available. Recommended collection: maritime/AIS

Red cell review: CONCUR

TLP:CLEAR