CVE-2026-130366: Update the deployed AdminNeo package
AdminNeo 5.9.1 fixes CVE-2026-130366. The maintainer disclosed the issue on November 16, 2026, and released 5.9.1 that day. The affected version range is earlier than 5.9.1.
The maintainer rates the issue High, with CVSS 3.1 score 8.1. VulnCheck’s CNA record, published November 17, assigns CVSS 4.0 score 9.2, Critical, and CVSS 3.1 score 8.1, High. Keep the scoring version with the rating when recording patch priority.
Locate the application that is actually served
Inventory each AdminNeo installation and its deployment method. Record its package version and the file or release directory selected by the web server. Include copies embedded in another application’s deployment bundle.
For a Composer installation, check the installed adminneo-org/adminneo package and its lockfile. A dependency update can leave an older compiled file in use: AdminNeo’s Composer documentation supports compiling the package into a separate PHP file. Record which compiled artifact the application loads and which package version produced it.
Replace the package and compiled artifact
Use 5.9.1 or a later supported release containing the fix. Obtain the application through the official download page or the existing managed package process. Preserve the required driver selection and review custom plugins before deployment.
If the installation compiles AdminNeo, rebuild that artifact from the updated dependency and deploy it with the release. Keep the prior configuration and a recovery copy outside the served directory. Older major versions can require migration changes; consult the upgrade guide before replacing a customized installation.
Verify the rollout
Compare the deployed artifact with the approved build record on every application node. Confirm that the web server selects the updated release and that any PHP opcode cache follows your normal deployment refresh procedure.
Use an authorized account for an ordinary login and a read-only administrative check. Record the package version, compiled artifact identity and node result. A successful login establishes normal operation; package and artifact evidence establish which release is deployed.
Acknowledgements
This post was created with assistance from AI.