Sunday, October 4, 2026 | War Day 217 | Truce Day 107
Shells land near journalists in Mayfadoun as southern bombardment continues
PROPOSED INDEX: 🟠 73/100 — HIGH
PROPOSED TREND: ↑ +1 point from the October 3 proposed rating of 72
SECURITY POSTURE: HIGH ALERT
Main areas of concern: Nabatieh governorate and the Tyre district of South Lebanon governorate.
Edition window: October 4, including overnight October 3–4 activity where identified. Source cutoff: 19:30 Beirut time on October 4. Later developments are outside this edition.
Rating basis: The numerical changes are proposed editorial judgments drawn from public reporting, using the supplied October 2 CIS scores as the baseline. They have not been calculated from proprietary CIS deployment reports or a supplied weighting formula. The headline follows the baseline convention of using the highest governorate rating. The comparison with October 3 is between two proposed estimates, rather than two officially published readings.
Executive assessment
The Sunday assessment remains HIGH, with particular concern about civilian activity near exposed southern locations. Shells reportedly landed close to media crews around Mayfadoun; the journalists escaped without injuries, according to the correspondent’s account. L’Orient Today’s Sunday evening recap
That reported outcome should not be mistaken for evidence of low exposure. The proposed upward adjustment reflects the continued difficulty of conducting ordinary movement and civilian work near affected areas. The response should be location-specific: verify access, reduce discretionary exposure and use current official instructions.
Regional diplomacy remains unresolved. Iran publicly conditioned reopening Hormuz on fulfillment of its demands, while a maritime notice reported tanker damage without establishing the incident date. Those developments inform regional monitoring without being counted as Lebanese strikes. Reuters/AFP on Iran’s position, Reuters on the tanker notice
Mayfadoun: shells near media crews
An Al-Jadeed account reproduced by Safir Al-Chamal reported three Israeli artillery shells directed toward teams from Al-Jadeed and Nabatieh media on Mayfadoun’s outskirts, with footage attributed to the channel. Report reproducing Al-Jadeed’s account
L’Orient Today’s evening recap reported that all four journalists left the area and that no one was injured, according to the journalist. The incident is attributed to the reporting team; this review does not independently establish intent. Sunday evening recap
Assessment: Civilian assignments in exposed areas require current access checks and a credible plan for interruption or withdrawal. The absence of injuries in this account does not diminish the importance of the reported near miss.
Southern field picture: overnight fire and daytime strikes
Mansouri and nearby communities
L’Orient Today’s southern correspondent reported at least 35 shells fired at Mansouri overnight. Its Sunday report also described artillery activity around Braasheet, Kfar Roummane, Arnoun–Kfar Tibnit and other southern locations, as well as helicopter fire around Zawtar al-Sharqiyah. Sunday field report
Assessment: Repeated coastal activity supports a proposed South Lebanon rating of 67/100, one point above Saturday’s proposed 66. District conditions, rather than the governorate average, should determine decisions about access and movement.
Airstrikes and a demolition reported Sunday
Lebanon24 reported airstrikes at Kfar Tibnit, Wadi al-Hujeir and Qantara, another strike between Ghandourieh and Qoussair, a demolition in Braasheet, and artillery fire at Mansouri and around Haddatha. Lebanon24’s October 4 field update
Assessment: Combining a known destination with an unverified connecting route creates an avoidable planning gap. Businesses and residents should confirm the full intended journey before departing.
Safety of civilian works
L’Orient Today reported shells hitting Shakra’s waste site, prompting firefighters to move workers and civilians away. It also described Mayfadoun as inhabited and outside the Israeli-designated line. That geographical characterization belongs to the outlet and is not an independently surveyed boundary. Sunday field report
Assessment: Municipal work, inspection visits and reporting assignments should be included in local exposure planning. Administrative or reported military boundaries are insufficient grounds for assuming safety.
Israeli military injuries: separate accident reports from combat claims
L’Orient Today reported an Israeli army statement issued Sunday about two soldiers injured in an operational accident on Friday, October 2, one seriously and one lightly. Sunday account
Daily Beirut had separately reported eight lightly injured soldiers in a Friday vehicle collision near Rabb al-Thalathin, citing Israeli Army Radio. Daily Beirut, published October 3
Assessment: These accounts are not reconciled. The figures are not added together, presented as Sunday combat casualties or treated as proof of a Hezbollah attack.
Diplomacy: a Friday call reported on Sunday
Jordan’s King Abdullah II and US Secretary of State Marco Rubio discussed the Lebanon–Israel framework and Hezbollah disarmament in a Friday call, according to official statements cited in Sunday reporting. Support for the Lebanese Army was also discussed. The account did not establish a new implemented withdrawal timetable. L’Orient Today’s diplomacy report
Assessment: The call belongs in the diplomatic context, with its event date preserved. Negotiating contact becomes a basis for lowering exposure only when accompanied by observable changes in access, activity or implementation.
Regional watch: Iran, Hormuz and Yemen
Iran states its conditions publicly
Reuters/AFP reporting carried by L’Orient Today said Parliament Speaker Mohammad Bagher Ghalibaf tied reopening Hormuz to fulfillment of seven Iranian conditions. A Foreign Ministry spokesperson said positions had been conveyed through mediators and further points remained to be communicated. Foreign Minister Abbas Araghchi advocated negotiations while warning of a response to renewed US military action. October 4 Iran report
Assessment: October 2’s description of Iranian silence should be replaced by the dated public position. This is an unresolved diplomatic track with escalation risk, rather than a confirmed breakdown of all contact.
Hormuz tanker notice: incident timing unresolved
Reuters reported that UKMTO announced Sunday that an unidentified projectile damaged a tanker’s engine room. The crew was reported safe, with no environmental impact reported at the time of the notice. The account did not specify when the incident occurred. Reuters tanker report
Assessment: This is recorded as a notice issued October 4. It is not assigned an assumed attack date, attributed to a perpetrator, or automatically counted as separate from the tanker incident referenced in the October 2 CIS edition.
Saudi energy claims and fighting in Yemen
AFP reporting described Houthi claims of a strike near Riyadh and the Saudi-led coalition’s rejection of those claims, while noting that flames had been observed at the facility. Observation of a fire does not resolve responsibility or establish damage to production. AFP account of the competing claims
Sunday’s evening recap separately reported Houthi gains affecting the Taiz–Aden supply route and a Yemeni government announcement of a broader counteroffensive. Sunday evening recap
Assessment: Lebanese firms with regional logistics exposure should verify shipments and transport arrangements. No domestic fuel shortage, airline cancellation or Lebanon-wide operational disruption is inferred from these reports.
Governorate security ratings
| Governorate | Proposed score / retained baseline | Band | Assessment basis |
|---|---|---|---|
| Nabatieh | 73 — proposed; +1 vs. proposed October 3 | 🟠 HIGH | Continued southern exposure, including the Mayfadoun media incident |
| South Lebanon | 67 — proposed; +1 vs. proposed October 3 | 🟠 HIGH | Repeated Mansouri activity in Tyre district |
| Beirut | 39 — October 2 baseline retained | 🟢 LOW | No score adjustment supported by this limited review |
| Beqaa | 32 — October 2 baseline retained | 🟢 LOW | No score adjustment supported by this limited review |
| Baalbek-Hermel | 31 — October 2 baseline retained | 🟢 LOW | No score adjustment supported by this limited review |
| Mount Lebanon | 26 — October 2 baseline retained | 🟢 LOW | No score adjustment supported by this limited review |
| Keserwan-Jbeil | 21 — October 2 baseline retained | 🟢 LOW | No score adjustment supported by this limited review |
| North Lebanon | 17 — October 2 baseline retained | ⚪ MINIMAL | No score adjustment supported by this limited review |
| Akkar | 16 — October 2 baseline retained | ⚪ MINIMAL | No score adjustment supported by this limited review |
Baseline: the supplied October 2 CIS edition. Proposed October 3 comparison: 72 for Nabatieh and 66 for South Lebanon. The retained figures are not independently refreshed assessments of all incidents in those governorates.
Scale: MINIMAL 0–20; LOW 21–40; MODERATE 41–60; HIGH 61–80; CRITICAL 81–100. HIGH is the applicable band. The score is not a probability, and it cannot determine personal safety at a particular address.
Statistics and chronology
| Metric | October 4 edition |
|---|---|
| Proposed national alert | 73/100 — HIGH, determined by the highest proposed governorate rating |
| Proposed day-on-day change | +1 point, from the October 3 proposed estimate |
| Proposed change from October 2 baseline | +3 points, from 70 |
| War-day count | 217, counting March 2, 2026 as Day 1 |
| Truce-day count | 107, counting June 20, 2026 as Day 1; a chronology marker, not a count of incident-free days |
| Daily Lebanese casualty total | Not established from the reviewed sources |
| Historical cumulative baseline | 4,386 killed; 12,407 injured, covering March 2–September 17; not an October 4 total |
MTV report citing the Health Ministry, September 17
No new independently verified cumulative total is established here. Later secondary reporting gives a different injury figure of 12,413; that discrepancy is preserved rather than silently resolved. Later secondary casualty reference
| Event date | Reported development | Interpretation |
|---|---|---|
| October 2; reported October 4 | Abdullah–Rubio call | Diplomatic context; event dated to Friday |
| October 2; reported October 4 | Two soldiers reportedly injured in an operational accident | Earlier incident; no inferred combat attribution |
| Overnight October 3–4 | Continued fire in southern communities | Relevant to Sunday access planning |
| October 4 | Shells reported near media crews at Mayfadoun | Civilian exposure concern |
| October 4 | Iran states conditions publicly | Replaces earlier silence framing |
| Incident date unspecified; notice October 4 | Tanker damage reported by UKMTO | No assumed attack date or perpetrator |
Practical security guidance
Affected southern communities: postpone discretionary visits to areas with current fire or demolition reports. Follow Lebanese Army, Civil Defence and municipality instructions. A boundary shown in news coverage is not an assurance that locations outside it are safe.
Damaged homes and properties: verify clearance and access before return. Keep away from debris, structurally damaged buildings and suspicious objects. Do not touch or move possible explosive remnants; report them to the authorities. Respect warnings and restricted areas. Lebanese Army explosive-hazard guidance
Media, aid organizations and contractors: reassess assignments near active incidents. Confirm access with the relevant authorities, maintain check-ins and prepare to suspend work if the local picture deteriorates. Credentials and a known civilian task do not themselves establish safe access.
Businesses and travelers: confirm the complete route shortly before departure and keep contingency arrangements current. Verify individual flight status with the airline and airport. The reviewed evidence does not establish airport operations, airport-road conditions or unrestricted flight availability.
Other governorates: use current local information and ordinary situational awareness. Baseline ratings should not substitute for checks relevant to a specific event, site or journey.
Watch points for the next edition
- New civilian casualty reports or damage to essential services.
- Further exposure of inhabited communities and civilian works.
- Verified changes to evacuation instructions, road access or displacement.
- Independent clarification of military incident and accident claims.
- Observable implementation of diplomatic commitments.
- Verified transport or supply effects from regional developments.
Emergency contacts in Lebanon
| Service | Number | Official reference |
|---|---|---|
| Lebanese Red Cross emergencies | 140 | Red Cross |
| Civil Defence | 125 | Civil Defence |
| Internal Security Forces | 112 | ISF |
| National psychological support and suicide prevention lifeline | 1564 | Ministry of Public Health |
CIS client contact: +961 3 539900 · info@cissecurity.net · cissecurity.net — carried forward from the supplied CIS edition.
Final assessment — October 4, 2026
The proposed national rating is 73/100 — HIGH, with Nabatieh highest and South Lebanon at 67/100 — HIGH. The additional point reflects the assessment of continued civilian exposure; it should not be read as a precisely measured increase in risk.
The priority remains checking local access and reducing avoidable movement near affected southern areas. Diplomatic contact is relevant, but a reduction in alert requires evidence of improvements that residents and operators can use. Any official CIS recalculation should replace the proposed figures consistently throughout this edition.
The CIS Lebanon Security Index™ is an informational security assessment. Conditions can change after the reporting cutoff. It is not a guarantee of safety or a substitute for official emergency instructions. This edition uses public reporting and the supplied CIS baseline; no proprietary field verification is claimed.
CIS Security — Because Your Safety Isn’t Optional — Since 1990
CIS Lebanon Security Index™ | October 4, 2026 | War Day 217 | Truce Day 107



