Enodia: Open-Source Go Tool Automates Service Inventory, EOL Tracking and CVE Correlation
A DevOps engineer running both a home lab and a large production environment grew frustrated with the inability to answer three simple questions: which exact versions of PostgreSQL, nginx and other services are deployed, which of them have reached or will soon reach end-of-life, and which carry known CVEs.
Initial attempts using Ansible playbooks to collect operating-system versions and export them into Google Sheets quickly proved unsustainable. The spreadsheets lacked diffing capabilities, contained no knowledge of support calendars, and could not reach services that do not expose SSH such as Jira, PostgreSQL, Redis or BMC interfaces.
After evaluating existing tools, none of which combined live service discovery, end-of-life calendars and CVE data, the engineer created enodia. The resulting single-binary CLI under the AGPL-3.0 licence reads a declarative YAML configuration describing every target and then interrogates each service with a purpose-built probe written in Go.
One hundred and twenty-three product-specific probes currently exist, covering Atlassian products, GitLab, Jenkins, TeamCity, SonarQube, Keycloak, Vault, Grafana, databases, message brokers, VMware ESXi and vCenter, Proxmox, NAS appliances, BMC cards, pfSense, RouterOS and 31 operating systems via SSH. A generic probe supports any remaining service via HTTP(S) plus regex or JSONPath extraction.
Enodia deliberately splits collection from evaluation. The command enodia collect produces an inventory.jsonl file containing only observed facts; enodia check later correlates those facts against support calendars and CVE databases. This separation allows inventory gathering inside closed networks and subsequent analysis where internet access or local CVE mirrors are available.
Instead of a single pass/fail verdict, the tool reports three independent axes: PATCH status (current or behind), LIFECYCLE status (active, security-only or EOL) and BRANCH status (latest, newer or newer LTS). These axes feed an overall severity of info, warn or fail that determines the process exit code, making the tool suitable for CI pipelines.
During development several non-obvious pitfalls were encountered and fixed. Early MySQL/MariaDB probes triggered the server’s max_connect_errors counter because they closed the connection before authentication; the current probe now performs a minimal login attempt so that the connection is counted as established. MariaDB’s version-string prefix “5.5.5-” caused older versions of enodia to misclassify servers as long-EOL MySQL 5.5.5. Debian point-release information is read from /etc/debian_version rather than the frozen VERSION_ID field. VMware “Update N” nomenclature is parsed into semantic versions so that 8.0 Update 3 is not reported newer than the calendar entry 8.0 U3k.
Support calendars are sourced primarily from endoflife.date, to which the author contributed full histories for Confluence, Bitbucket and Bamboo plus new entries for Jira Service Management and pgAdmin. CVE data is pulled from both NVD and Russia’s FSTEC BDU; package-level vulnerabilities for ten distributions are obtained via their native OVAL or Security Tracker feeds. All CVE databases can be updated once and then used offline inside air-gapped environments.
Related articles
Critical PHP Vulnerability to Receive Patch on November 19 at 23:00 JST
A critical-severity vulnerability has been identified in the PHP scripting language, affecting all supported branches. The PHP security team has pre-announced a security update release scheduled for 14:00-14:30 UTC on November 19, which corresponds to 23:00-23:30 Japan Standard Time. Although the maximum severity rating is critical, the flaw does not impact default configurations and requires uncommon system setups to be exploitable. No specific technical details, CVE identifiers, or attack vectors have been disclosed ahead of the patch. The update forms part of PHP's regular four-week release cycle. This follows another serious PHP flaw called PHP2Shell that required emergency remediation in October. Organizations are strongly advised to prepare for immediate deployment once the fix becomes available.
Java4Shell Vulnerability Enables Remote Code Execution Without Authentication Across Keycloak, Jira, Confluence and Other Enterprise Platforms
A critical flaw tracked as CVE-2026-114938 and dubbed Java4Shell allows unauthenticated remote code execution on multiple widely deployed Java applications including Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate when running in their default configurations. The root cause lies in a buffer overflow inside the AVX-512-accelerated Base64 decoder of HotSpot JVM on x86-64 processors that support the VBMI instruction set. Malformed Base64 strings ending with an extra equals sign cause the decoder to write 62 or 63 bytes past the allocated output buffer before the Java runtime rejects the input. Because several authentication-related components such as Basic Auth headers, SAML artifacts and CSRF tokens are decoded before any session or access-control checks occur, the vulnerable code path executes with attacker-controlled data prior to authentication. The issue affects Java 17.0.6 and later releases on lines 21, 25 and 27 when running on Intel Xeon Ice Lake or newer and AMD Zen 4 CPUs; ARM64 systems remain unaffected. Oracle and OpenJDK released fixes on 18 November, CISA issued an urgent advisory the same day, and Amazon has already updated Corretto builds while Red Hat continues work on its distributions.
Attackers Exploit Critical Apache Roller Flaw CVE-2026-129448 for Unauthenticated Remote Code Execution
Cybercriminals are actively exploiting a critical vulnerability in Apache Roller that allows remote code execution on the server without any credentials. The Java-based blogging platform received CVE-2026-129448 with a CVSS score of 9.8, and the Apache Software Foundation has confirmed active exploitation in the wild. The attack path targets the XML-RPC endpoint, which accepts vendor extension types and deserializes requests before performing authentication. The flaw affects versions 4.0.0 through 6.1.4, expanding the scope beyond the earlier CVE-2026-82384 that only listed version 6.1.5 as affected. Disabling XML-RPC through the admin interface provides no protection on older versions because deserialization occurs before the setting is checked. The recommended fix is upgrading to version 6.1.6 or later, which properly disables extension types and enforces the configuration. Organizations unable to update immediately should set enabledForExtensions to false in web.xml or remove the XML-RPC servlet mapping.
PHP Prepares Critical Patches for All Supported Versions One Month After Emergency Update
The PHP development team announced on November 18 that it will release updates for all supported interpreter versions to address multiple vulnerabilities, including critical ones. The fixes target a use-after-free flaw in file upload progress tracking that can lead to remote code execution when specific session serialization formats are combined. This comes shortly after emergency patches issued on October 21 resolved two remote code execution issues collectively known as PHP2Shell. The new vulnerability, tracked as CVE-2026-115560 with a CVSS score of 9.8, arises when applications switch session formats from php_binary or php_serialize to php after upload tracking has begun. Developers are advised to disable session.upload_progress.enabled until patches are applied and verified. Releases are scheduled for November 19 between 17:00 and 17:30 Moscow time, accompanied by a detailed security bulletin.