Tech Blog

everyWAN Blog

Technology, cybersecurity and IT trends that matter

Deep Analysis
Cybersecurity
IT Trends
Filter by:
Escritorio de madera vacío con un portátil abierto y un ratón, y una silla retirada
9 min read

Tailscale checked the path as text and opened it as root

Four Tailscale security bulletins dated 26 October 2026 and a fix tagged last night: the SSH server validated Unix socket paths lexically and then performed the operations as root, with the Docker socket and the tailscaled local API on the other side. What the four bulletins say, what the 42 commits in the fix tell you — including the session recording that could differ from what actually ran — why a mesh is not segmentation, and six checks for this week that do not require waiting for an upgrade.

Pasillo de un archivo con estanterías llenas de cajas y archivadores etiquetados
9 min read

Your inventory has no line for Brotli

CVE-2026-111497 is an out-of-bounds write in Google's Brotli decoder: eight bytes of internal buffer from which Node.js, Bun, Python, Envoy, Istio, .NET, FFmpeg, ClickHouse and Apache Arrow all hang. In four days it had five names — Node2Shell, Python2Shell, HTTP2Shell, Brotli2Shell and Broccoli2Shell — and each one was somebody discovering the blast radius was wider than they thought. The fix had been public upstream since 27 February. The word that repeats across every advisory is "bundled": Arrow carries Brotli 1.0.9 inside it, .NET carries its own copy and ClickHouse maintains a fork. Why "is it patched?" has no single answer but eight separate clocks, why you are the one making the request rather than your perimeter, and the five-question census with the exact commands.

Armario de comunicaciones mural de una oficina, con un conmutador de red, un router y un módem conectados con cables de cobre
10 min read

Two hours from a PHP website to the domain hashes

On 21 October 2026 CISA asked for something nobody writes lightly: anyone who cannot patch PHP immediately, or who is still on 8.1 or earlier, should take their PHP-based systems off the network. These are CVE-2026-109618 and CVE-2026-109619, both scoring 9.2 on CVSS v4.0, and the details leaked before the patch existed. But the door is not what interests us: in the case Unit 42 documents against a European government entity, two hours passed between the break-in and the password hashes, the MFA secrets and an NTLM tunnel into Active Directory. PHP did not open that path. With the branch table, the mitigations that do not mitigate, and the twenty-minute check.

Pasillo de un centro de datos con filas de armarios de servidores y bandeja de cableado en el techo
10 min read

Your scanner says zero criticals and the exploit gets root

On 21 October 2026 the Zero Day Initiative sent five Linux kernel bug reports to the security team and, by mistake, to the public development lists. Three carried full proof-of-concept code. None has a CVE, because the kernel only assigns a number once the fix is already in a stable tree. And one of them has already produced root on AlmaLinux 8, 9 and 10, Debian 12 and 13 and Ubuntu 24.04 and 26.04, bypassing the Dirty Frag fix. We explain why the 9.0 probably does not affect you and the 7.8 does, what to check on each machine and the traps in checking it, and why the number that eventually shows up in your scanner is not a warning but a receipt.

Puesto de trabajo de oficina con un portátil, dos monitores, teclado y una libreta sobre una mesa de madera clara
9 min read

The signature was valid; the DLL next to it was not

On 19 October 2026 Siemens confirmed in-the-wild exploitation of CVE-2026-110936 in its Software Center. What ran on the victims' machines was a genuine, correctly signed copy of the program: the attacker only had to drop an archive.dll in the same folder. If your application control authorises "anything signed by a known publisher", this campaign passes the filter by design, not by failure. We explain what a digital signature answers and what it does not, why the CVSS vector says "local" while your patch queue reads that as "no rush", the three behavioural signals that do leave a trail, and the three questions you can answer this afternoon.

Pasillo entre armarios de servidores encendidos en una sala técnica real, con un taburete de madera olvidado en el pasillo
10 min read

SafePay's five doors: not one of them is from 2026

The joint advisory on SafePay published on 20 October 2026 — FBI, CISA, the Secret Service and three European police bodies, at least 600 victims since August 2024 — lists five exploited vulnerabilities. Not one is from 2026 or 2025: three sit in the firewall that lets people in and two in the backup server that was meant to save you. The detail almost nobody has covered is that NAS devices do not get their files deleted: they get reset to factory settings. We go through the five doors with their fixed versions, why patching does not close the session already taken, when NOT to patch first thing tomorrow, and the eight checks we run ourselves.

Armario de comunicaciones abierto con un panel de parcheo y decenas de latiguillos azules sin ordenar
9 min read

Redis: the patch had been out for 164 days

On 16 and 17 October 2026 a set of decoys recorded the first exploitation attempts against CVE-2026-25243, the flaw in Redis's RESTORE command. The patch was published on 5 May: 164 days earlier. Throughout those 164 days the flaw carried two scores — 7.7 from the party that published it and 8.8 from the NVD — that cannot be compared because they come from two different versions of CVSS; plus a CISA record dated 6 May that to this day still says "no known exploitation". We go through why those two scores cannot be subtracted from each other, why "requires authentication" does less work than you think, the six patched branches the CVE record itself never mentions, and the five checks that close the matter.

Pasillo de estanterías compactas de archivo, cerradas, con sus manivelas de accionamiento
9 min read

The advisory came 47 days late and your logs last 30

On 15 October BeyondTrust published CVE-2026-102764, a critical flaw in its remote support product that an espionage group had been exploiting since 29 August: 47 days of head start. CISA added it to the known exploited vulnerabilities catalogue on the 16th and gave federal agencies a deadline of today, 19 October. Patching is the easy half; the other half is the day-48 question — were we in it? — and the patch does not answer it, what answers it is what you decided months ago about log retention. With Entra ID defaults (7 days on Free, 30 on P1 and P2) and Defender XDR's 30 days of raw data, 29 August no longer exists in your identity log or your EDR. And Microsoft's own documentation says it plainly: retention is not retroactive.

Estanterías metálicas de una sala de archivo con cajas y legajos de documentos
9 min read

Nextcloud and CVE-2026-110447: the hole opens when something goes down

On 14 October Collabora published the advisory for CVE-2026-110447: 9.2 out of 10, unauthenticated command injection in an optional Nextcloud app plenty of people installed one afternoon. And one sentence in the advisory that changes the whole job: "the attack only works while the built-in CODE server is not running". The exploitation window is your maintenance window: the restart, the upgrade, the process that died at three in the morning and nobody saw because monitoring stayed green. Why the 9.2 carries a letter almost nobody reads, why disabling the app is not enough, what to look for if it already happened, and when this is not your problem.

Armario de red de pared con equipamiento y cableado a la vista
6 min read

PAN-OS CVE-2026-0322: there is no single patch, there are twenty

Palo Alto published the advisory on 14 October 2026 with exploitation already observed, and CISA added it to the KEV the same day with a 17 October federal deadline and the forensic triage flag set. When you open the advisory looking for the patch, you do not find one: you find twenty fixed versions across five branches, six in 11.1 alone, because the vendor fixes on the maintenance train you are already on. What the advisory actually says, what pushes the 8.6 up and down at once, why Panorama is the piece that hurts most, and the five things we would do this week.

Armario de distribución de fibra abierto, con bandejas, latiguillos y módulos a la vista
9 min read

Two 10.0s in Arista EOS and no hotfix: your config decides, not your version

Two 10.0-out-of-10 flaws in data centre switches, both without a hotfix, published in September and with remarkably little noise around them. The reason for that silence is also the interesting part: nobody knows how many devices are affected, because exposure is not decided by the installed version but by two configuration lines almost nobody inventories. What the Arista advisories actually say, why they are 10.0 and not 9.8, the twenty-second check per device, and the three fields missing from any network inventory.

Interior de un armario de comunicaciones con regletas de conexión, latiguillos y un equipo montado en la pared
9 min read

The fix needs no window and no restart, which is why it may not be in place

On 14 October Cisco published a 9.8 flaw in its email gateway, exploited before the advisory went out. The striking part is not the score: it is that the fix ships as a scanning-engine package that "does not require a software upgrade or a product restart". That sounds like good news, and it is precisely what keeps it out of your patching process, which is built from tickets, windows and restarts. What to look at before that engine changes version, and why for an arbitrary file write "patched" does not mean "clean".

Escritorio con un portátil de pantalla apagada, una libreta abierta con anotaciones a mano y una taza de café
9 min read

The SDK behind your AI agents has six new advisories. Your scanner says zero

Between 28 September and 5 October 2026, the Model Context Protocol Python SDK published six security advisories, three of them scored 7.5. As of 12 October none of the six appears in OSV, nor in the global GitHub database that fires Dependabot, nor in the PyPI API that pip-audit queries by default; the only one carrying a CVE is not in the NVD either. We checked it with two public API calls you can repeat in a minute. And two of the six state in writing that upgrading, on its own, fixes nothing.

Cuarto de cableado de un edificio con un conmutador sobre una balda, bloques de conexión antiguos y latiguillos sueltos
9 min read

Only one of the eight exploited flaws is in a network appliance

Joint advisory AA26-281A, signed in Spain by the CNI, lists eight CVEs successfully exploited by Flax Typhoon. One is in a network appliance, a Pulse Connect Secure; the other seven are software on servers: Bash and BIND ship with the OS, Struts travels inside a Java application, and ProFTPD, GitLab, ONLYOFFICE Docs and Strapi were stood up by someone on a specific day. Three were already in CISA's catalogue, two since November 2021 with the ransomware flag set. The counts done on the catalogue JSON, with the commands, and the three questions that actually build that inventory.

Pasillo de una sala de servidores a oscuras, iluminado solo por los pilotos de los equipos, con un taburete vacío olvidado en medio
9 min read

The miner switches off when you open Task Manager

The AhsayCBS intrusion Huntress documented on 8 October 2026 included a PowerShell script that stops the miner service when you open Task Manager, restarts it when you close it, and kills Task Manager itself at six in the evening. What the attacker modelled was not the antivirus: it was the working hours of whoever looks. Why interactive checking is not detection, and a ten-minute test to find out whether yours is.

Hilera de volantes de válvula industriales en un nicho de hormigón, fotografía documental en blanco y negro
9 min read

FortiMail: patch out on the 2nd, advisory on the 7th, mitigation still on

On 1 October Fortinet published a 9.8 flaw in FortiMail, exploited and with no fixed release. The only mitigation available was to switch off IBE encryption: the channel your company uses to send confidential documents to people outside it. The fixed release notes are dated 2 October; the advisory did not say so until the 7th. If your trigger for removing the mitigation is the advisory, your clock runs five days behind. Inside: the branch table (including the branch that gets no patch), the indicators Fortinet did publish, what the public documentation does NOT answer, and a six-line record so a temporary mitigation does not last six months.

Pasillo de un centro de datos con un rack abierto, un carro de consola con monitor y teclado, y una silla vacía
9 min read

A VM escape with no CVE and no patch: what root on a Proxmox node reaches

On Tuesday 6 October 2026 The Register reported that a researcher claims a guest-to-host escape in KVM, that Vercel's CEO confirmed it inside their bounty programme, and named Proxmox among those relying on KVM. There is no CVE, no patch and no technical detail. Since there is nothing to patch, what is measurable today is the radius: Proxmox VE's documentation says QEMU runs as a root process, so it is one hop and not two; and root on one node reads /etc/pve/priv, which pmxcfs replicates in real time to every node. Inside: the table of ten files with their official descriptions, why the backup password sits there "in plain text" next to the encryption key, and the rotation list, line by line, with what each one costs.

Armario de comunicaciones real con switch, regletas de conexión y latiguillos de fibra sobre pared de contrachapado
8 min read

Thirteen of ClearPass's twenty-eight flaws are in the agent, not the server

On 6 October 2026 HPE published advisory HPESBNW05158 with 28 ClearPass Policy Manager vulnerabilities: 10 critical, 11 high and 7 medium. The interim mitigation the advisory itself recommends names the CLI and the web-based management interface, both of them on the server. We classified all 28 by the component HPE names in each title: thirteen live in the OnGuard agent or the client software, which is to say on the laptops. Two of those thirteen are 9.8 criticals needing no prior authentication. Inside: the table of the thirteen, the end-of-maintenance note that decides whether yours is a patch or a branch jump, and the question worth answering before the change window.

Técnico agachado con un portátil delante de un armario de servidores abierto en una sala técnica
9 min read

Read-only in the backup console was not read-only

On 6 October 2026 Veeam published advisory KB4934 with three Backup & Replication vulnerabilities. Two of the three are triggered by the same role: Backup Viewer, the one handed out without a second thought because it is there for looking. The worst reaches 9.4 and runs code on the backup server; the other, scored 6.1, allows deleting the Enterprise Manager master key, which is the documented mechanism for decrypting a backup when the password is lost. Inside: the table of all three CVEs with their vectors, why PR:L is the part that matters, and the role assignment list no recovery plan includes.

Armario de red de oficina abierto, con un conmutador y una maraña de latiguillos acumulados dentro
9 min read

Eight products, nineteen versions: Atlassian's advisory tells you what to do, not what you have

The CVE-2026-21589 advisory, dated 5 October 2026, affects eight self-hosted Atlassian products: Bitbucket, Confluence, Jira Software, Jira Service Management, Bamboo, Crowd, Crucible and Fisheye. It is one of the thorough ones: nineteen fixed versions, temporary mitigations if you cannot patch —including taking the instance off the internet— and a method for hunting traces in your access logs. All three instructions start from a question the vendor cannot answer for you. Inside: the version table, why "we are on 10.2" points at three different products, and Atlassian's thirteen entries in CISA's KEV catalogue.

Subscribe to our newsletter

To receive IT stories, everyWAN news and exclusive subscriber offers, sign up to our mailing list

Minorisa de Sistemas Informaticos y Gestión S.L. © 2026
everyWAN
everyWAN