Tech Blog

everyWAN Blog

Technology, cybersecurity and IT trends that matter

Deep Analysis
Cybersecurity
IT Trends
Filter by:
Frente de un fichero de biblioteca de madera con decenas de cajones de fichas
9 min read

What to reindex after PostgreSQL's 52-CVE batch

On 12 November PostgreSQL released 18.7, 17.12, 16.16, 15.20 and 14.25 with 52 CVEs fixed. The package and the restart close all 52, but the same batch carries five index-corruption items that do not fix themselves: GIN, pg_trgm, bpchar and TOAST-table indexes stay corrupt until you run REINDEX by hand. Inside: the right order of operations, four census queries that change nothing, the bpchar nuance that rules out CHAR(n), and why your incremental backup chain stopped being a chain.

Sala de ordenadores con filas de armarios de servidores y carteles escritos a mano sobre cada fila
8 min read

Zabbix 8.0 wants PostgreSQL 15 and Ubuntu 22.04 ships 14

Zabbix 8.0 LTS shipped on 5 November 2026 with OpenTelemetry, ClickHouse and an MCP server. All of that has to be built. What arrives unasked are six version floors rising underneath: PostgreSQL 13 → 15, MySQL 8.0.30 → 8.4.0, MariaDB 10.5 → 10.11, TimescaleDB 2.13 → 2.20, Elasticsearch 7.0 → 8.0 and PHP 8.0 → 8.2. Inside: the minimums table with its ranges closed at the top, which of the six cannot be waived by any parameter, what each distribution archive actually serves (Ubuntu 22.04 meets none of the four), our own measurement in the Zabbix repository of where they drew the line, why two things expire on 12 November, and five checks before you set a date.

Sala de servidores con equipos de varias generaciones conviviendo en los mismos bastidores
6 min read

PostgreSQL 14 goes end-of-life on 12 November and nothing will tell your server

On 12 November PostgreSQL 14 gets its final minor release and loses support. Nothing falls over that day, and that is the trap. On a managed database the date turns into money: AWS bills extended support as a separate line item, $0.100 per vCPU-hour in its published example, and reserved instance discounts do not apply to it. On your own server the date turns into nothing at all: no bill, no alert and no security patches. The cloud charges you and, by charging you, tells you.

Técnico agachado con un portátil trabajando en la parte trasera de un rack de servidores
5 min read

REPLICATION was never a read-only privilege: PostgreSQL closed a twelve-year dlopen()

On 13 August PostgreSQL shipped 18.6, 17.11, 16.15, 15.19 and 14.24. Among the CVEs they close there is one that is not about buffer overflows: any account holding the REPLICATION attribute could name as its logical decoding plugin any file visible to the system, and the server would load it and run its code as the operating system user. The patch adds a whitelist with two entries by default: if your change data capture uses decoderbufs or wal2json, it stops your replication until somebody edits postgresql.conf.

Sala de archivo de una oficina con estanterías metálicas llenas de cajas de cartón y carpetas, y una caja abierta sobre una mesa de trabajo
9 min read

"The column was encrypted": pgcrypto was storing cleartext and nobody noticed

On 13 August PostgreSQL closed 28 CVEs in one go. One of them is not a buffer overflow: when OpenSSL rejected the requested cipher, pgcrypto never checked the answer and wrote the value into your "encrypted" column with a trivial XOR. Neither the INSERT nor the SELECT failed. What triggers it, why the day it broke was not the day the code was written, and which version you are really running if you install from Debian rather than PGDG.

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