Skip to content
CVE-2026-130380: Roll out AdminNeo 5.9.1 across application nodes

CVE-2026-130380: Roll out AdminNeo 5.9.1 across application nodes

November 19, 2026

CVE-2026-130380 is fixed in AdminNeo 5.9.1, released November 16, 2026. The maintainer disclosed the issue that day and lists versions before 5.9.1 as affected.

The maintainer’s rating is High, CVSS 3.1 score 8.1. The VulnCheck CNA record, published November 17, also records CVSS 3.1 score 8.1, High, and assigns CVSS 4.0 score 9.2, Critical. These are separate scoring-system results.

Build a node inventory

List every host or container serving AdminNeo, including administrative deployments outside the main application fleet. For each one, record the application version, deployment artifact and owner. Check the installed package or release manifest on the serving node rather than relying on a build workstation’s dependency list.

Where AdminNeo is bundled as a single PHP file, identify its build version and the active file location. For a container deployment, record the running image digest and the build record that identifies the bundled AdminNeo version. An image tag alone does not prove the running container was replaced.

Deploy the fixed application

Select 5.9.1 or a later supported release containing the fix from the official distribution. Keep the deployment’s intended database drivers and configuration, and verify customizations against the upgrade guide. A Composer-based build that produces a compiled PHP file must regenerate and deploy that file as part of the update.

Roll through the nodes using the normal maintenance procedure. Keep an explicit pending entry for any stopped node, standby deployment or scheduled workload that could later start with an older application bundle. Update the corresponding deployment template as well as the currently running instance.

Confirm completion on every node

Compare each active artifact with the approved release, then perform an ordinary authorized login and read-only health check. Check normal application logs for startup or compatibility errors.

Retain the installed version and artifact identity with the deployment result for each node. Keep recovery material outside web-served directories, and preserve access restrictions on the administrative application throughout the rollout.

Acknowledgements

This post was created with assistance from AI.

Last updated on