
🔥 CyberForge Weekly CVE Rundown #004 — The Sunday Debrief 🗓️ 28 September–3 October 2026 Six days. Seven CVEs. One defender-focused debrief. This week crossed mail servers, router management, an embedded kernel, database exports and a helpdesk breach. Three CVE IDs are in CISA KEV. The Forge lesson: identify the reachable feature, preserve the evidence and verify which boundary the remedy actually repairs. 📚 The six-day rundown 1️⃣ Monday — Day #063 — CVE-2026-100741 hMailServer — JScript eval injection On Windows 6.0.0–6.3.3, unauthenticated mail input can become service-account code execution. This requires non-default JScript event scripting and an affected handler; the authentication route must name an active account. ⚠️ Why it made the list: Configuration decides exposure; service identity decides authority. 🛡️ Defender move: Follow the manual 6.3.4 upgrade guidance, including backups and database migration. 📌 Status: Fix verified; not KEV-listed, checked 4 October. 🔗 Full post / primary source: hMailServer CNA record: https://cveawg.mitre.org/api/cve/CVE-2026-100741 6.3.4 release guidance: https://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.4 2️⃣ Tuesday — Day #064 — CVE-2026-101001 Netcore NBR200V2 — Command evaluation before authorisation Firmware 1.3.241127.071246 permits unauthenticated remote command injection. The researcher reports evaluation before the permission check; a refusal can follow execution. ⚠️ Why it made the list: An error response cannot prove that nothing happened. 🛡️ Defender move: Restrict web management, investigate prior reachability and request a verified repair. 📌 Status: CNA-reported public exploit; no fixed firmware verified; not KEV-listed on 4 October. 🔗 Full post / primary source: VulDB CNA record and researcher references: https://cveawg.mitre.org/api/cve/CVE-2026-101001 3️⃣ Wednesday — Day #065 — CVE-2026-102710 Eclipse ThreadX — Trace callback crosses into kernel privilege An attacker who controls a loaded user-mode, memory-protected module can register a callback invoked with kernel privilege when the trace buffer wraps. This requires TX_ENABLE_EVENT_TRACE. ⚠️ Why it made the list: Memory protection depends on the callback boundary holding. 🛡️ Defender move: Review resident tracing and module controls; seek a CVE-specific OEM repair. 📌 Status: CNA-reported runtime reproduction; repair unverified; not KEV-listed on 4 October. 🔗 Full post / primary source: Eclipse CNA record: https://cveawg.mitre.org/api/cve/CVE-2026-102710 4️⃣ Thursday — Day #066 — CVE-2026-71379 Toptech TMS7 / TopHAT — Unauthenticated database export In 7.6.3, a crafted POST can export arbitrary database tables without authentication. This CVE establishes data exposure; the wider advisory's code-execution claims belong to other entries. ⚠️ Why it made the list: Export functionality needs its own access checks. 🛡️ Defender move: Coordinate the move to 7.8, preserve export evidence and validate operations. 📌 Status: Remedy confirmed; not KEV-listed on 4 October. 🔗 Full post / primary source: CISA advisory and CVE-specific entries: https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-272-02.json 5️⃣ Friday — Day #067 — CVE-2026-104286 FortiMail — Exploited arbitrary file write Unauthenticated HTTP/HTTPS requests can write files through traversal and NULL-byte handling. Fortinet confirms exploitation. ⚠️ Why it made the list: The current remedy still requires a workaround. 🛡️ Defender move: Disable IBE or restrict internet webmail access using vendor guidance; preserve incident evidence. 📌 Status: KEV-listed; 8.0.2, 7.6.7 and 7.4.9 still marked upcoming on 4 October; source matrices conflict. 🔗 Full post / primary source. Fortinet PSIRT matrix, workarounds and indicators: https://fortiguard.fortinet.com/psirt/FG-IR-26-175 6️⃣ Saturday — Day #068 — CVE-2026-102489 + CVE-2026-102490 Zammad — Session hijack followed by local escalation DIVD reports session hijacking to execution as zammad, then local escalation to root. Its first-flaw score requires passive interaction; the escalation requires existing server access. ⚠️ Why it made the list: Two different boundaries form the reported chain. 🛡️ Defender move: Follow the 7.2.0 recommendation and investigate; the local-escalation fix remains unverified. 📌 Status: Both KEV-listed on 4 October; vendor says the first flaw is not exploitable on 7.0+. 🔗 Full post / primary source: DIVD case: https://csirt.divd.nl/cases/DIVD-2026-00015/ Later vendor update: https://community.zammad.org/t/21297/3 🔄 Since the original posts. Updated recap: Sunday's focused check refreshed CNA/NVD records, KEV and selected project/vendor guidance. Other technical detail retains its daily source date. ThreadX released 6.5.2.202603 on 2 October, but its nine-CVE fix list omits CVE-2026-102710. The trace callback path remains in the inspected tag; this pass cannot certify that release as its repair. 🔗Project release: https://github.com/eclipse-threadx/threadx/releases/tag/v6.5.2.202603_rel FortiMail's current workaround explicitly addresses webmail exposure and also offers a scoped WAF rule. Its release targets remain upcoming. 🔗 PSIRT guidance: https://fortiguard.fortinet.com/psirt/FG-IR-26-175 KEV's federal due-date fields are 4 October for FortiMail and 5 October for both Zammad IDs. Applicable organisations should act within that scope; exposed private-sector systems also deserve prompt triage. 🔗 CISA catalogue: https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json 🏆 This week's Forge honours. 🚨 Most Severe — Joint honour: Netcore and Toptech Their CNAs both assign CVSS v3.1 10.0, the highest verified v3.1 scores here. This is a same-version comparison, not a universal urgency ranking. Toptech's score does not establish RCE through its export CVE. Sources: their linked CNA/advisory records. 🧩 Most Interesting Attack Chain — Zammad duo DIVD/CISA connect application-account execution to a separate local root escalation. Keeping those stages distinct improves investigation and prevents a 7.2.0 recommendation becoming an unsupported “both fixed” claim. 🛡️ Most Defender-Relevant — FortiMail For affected mail-gateway operators, confirmed exploitation, available workarounds, vendor indicators and forthcoming patches make containment and historical review immediate work. 💜 CyberForge Pick of the Week. CVE-2026-102710 — Eclipse ThreadX's delayed privilege crossing Lee's pick, and a memorable lesson: a callback registered earlier can execute later with greater authority. Eclipse reports kernel privilege in its runtime capture; initial module control is still required. Forge interpretation: Ask who supplied the callback, when it was registered and which build permits that service. The thread active at a later fault may not identify the original registration. A feature intended to help observation can become part of the trust boundary itself. 🧠 What connected the week. hMailServer's scripts and ThreadX's callbacks show input crossing into greater authority. Netcore adds the danger of checking permission too late. These are different products and mechanisms; this week's selections establish no shared actor or campaign. 🛡️ The defender's Monday shortlist: 1️⃣ Act on exploited exposure now: FortiMail workaround plus triage; Zammad upgrade guidance plus separate local-escalation investigation. 2️⃣ Make repair verifiable: Plan hMailServer's backed-up manual upgrade and Toptech's controlled 7.8 change; obtain exact Netcore/ThreadX repair confirmation. 3️⃣ Record configuration: JScript handlers, reachable router management, ThreadX module/tracing builds and Zammad runtime versions all change scope. 🔥 CyberForge closing thought. Sunday's value is a clearer Monday: the right asset, the right evidence and a remedy tied to the actual flaw. > A new version is a lead. A verified repair is evidence. #CyberSecurity #CVE #WeeklyRundown #ThreatHunting #BlueTeam #CyberForge
Post summary
This weekly rundown covers seven CVEs across multiple products, highlighting three actively exploited vulnerabilities listed in CISA KEV (FortiMail, Zammad duo) with confirmed exploitation, available workarounds, and technical details, alongside patches and mitigations for others.




