BlackTree Security · Infrastructure · Automation · AI

BlackTree — Independent Technology Analysis

BlackTree Editorial

Independent technology intelligence Analysis · Technical guides · Homelab · Legacy systems

Security, systems and emerging technology

Know the signal behind the incident.

Independent analysis for the people who build, secure and operate technology, with the clarity to inform action and the technical depth to earn trust.

Evidence-linked Operational context Independent

Tracebit Tests How Decoys Change an AI Attacker’s Decisions

Tracebit’s October cloud experiment reports fewer completed objectives and higher costs. The baseline, model differences and denominators matter.

Read the article ↗

Current reporting

Latest intelligence

View all articles ↗

Expressway Fixes Need More Than One Version Check

Cisco Expressway’s October security releases cover several different boundaries: access to a clustered database service, weaknesses across clustered and standalone systems, information exposed during provisioning, and PHP embedded in the product. A team can complete one of those checks and still have work left. Cisco’s PHP matrix has also moved on since the initial release, so an older copy of the product table is insufficient.

Cisco’s 21 October database-service advisory identifies CVE-2026-76466, rated critical at 9.8. The affected set is Expressway Core and Edge, known as Expressway-C and Expressway-E, running a vulnerable release in a cluster. Both virtual installations and physical appliances are included.

An attacker needs network access to the database service and possession of persistent cookies. Invoking particular remote procedure calls can then execute operating-system commands as root. Cisco also says client certificates are not validated when the clustering TLS Verify Mode is enabled. An enabled setting therefore does not demonstrate that this validation is actually enforced on an affected release. The unauthenticated classification must be read alongside the cookie-possession prerequisite.

The database table lists X15.5.20 as the first correction for its X15.5.3-and-earlier row. X14 and earlier must migrate to a fixed release. Cisco reports no workaround that resolves the vulnerability. Network restrictions may reduce exposure as part of an authorised response, but they do not replace the listed software correction or establish that earlier access did not occur.

The broader Expressway hardening advisory has a different configuration scope. It includes virtual and appliance Core…

1 Nov 2026 · 4 min read

Snort 3 Fixes Need the Product’s Update Path

Cisco’s October Snort 3 update reaches both the open-source inspection engine and products that embed it. The upstream version number is only one part of the remediation decision. Appliance software, inspection packages,…

1 Nov 2026 · 5 min read

Thunderbird Fixes Unwanted Connections and Message Leaks

Thunderbird’s latest desktop security updates address more than malicious content inside an email. Displaying a message can trigger an unwanted connection, a reply can carry material from another message, and calendar or…

1 Nov 2026 · 5 min read

Tomcat’s Login and HTTP/2 Fixes Need Different Checks

Tomcat’s October corrections address two different security decisions: whether one user can receive material belonging to another request, and whether a particular directory-backed login accepts an incorrect password. An inventory that records…

1 Nov 2026 · 4 min read

Check Mattermost’s Build Before November’s Disclosures

Mattermost’s November disclosure dates should be used to plan a follow-up review, not to postpone security updates that are already available. The useful question is which installed release addresses each issue. A…

1 Nov 2026 · 3 min read

Revised reporting

Recently updated

View all articles

Geographic context

Regional intelligence

Browse all articles ↗

Coverage leaders

Vendor intelligence

Browse all articles ↗

Practical archive

Lab &
Legacy

Field-tested guidance for keeping older systems useful, secure and reliable long after mainstream documentation has moved on. Practical fixes, automation and deployment notes are drawn from real environments and written for the operators who still maintain them.