dbcve.org
Nginx AgentWeb server / proxy · F5

CVE-2026-60062

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-15
Fix available
A fix is available. Upgrade to 2.22.2 / 2.46.7 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The NGINX Agent config_dirs directive allows a low-privileged attacker to gain limited read and write access to files outside of the designated secure directory. The config_dirs directive required for this issue can also be configured through NGINX Instance Manager. A successful exploit may allow an attacker to cross a security boundary. Impact: A remotely authenticated low-privileged attacker could gain limited read and write access outside of the list of directories specified in the NGINX Agent configuration. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The NGINX Agent config_dirs directive contains a path traversal vulnerability allowing an authenticated low-privileged attacker to read and write files outside the designated secure directories. The vulnerable directive can be configured through NGINX Instance Manager, and successful exploitation allows crossing the security boundary between the intended secure directory list and the filesystem.

MitigationRestrict the config_dirs directive to only the minimum required directories, implement strict path validation (canonicalization and boundary checking), and ensure least-privilege access controls for NGINX Agent and Instance Manager authentication.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nginx AgentWeb server / proxy
Affected:>= 2.37.0, < 2.46.7
Nginx Instance ManagerWeb server / proxy
Affected:>= 2.17.1, < 2.22.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify NGINX Agent installation
    Run 'nginx-agent --version' or check for the nginx-agent binary in common locations such as /usr/sbin/nginx-agent, /usr/local/bin/nginx-agent, or via package manager listings (dpkg -l | grep nginx-agent, rpm -qa | grep nginx-agent)
    Affected if NGINX Agent is installed and the version falls within the affected range (compare your installed version to known affected versions if available)
  2. Check if config_dirs directive is configured
    Examine NGINX Agent configuration files (typically /etc/nginx-agent/nginx-agent.conf or /etc/nginx-agent.conf) and look for the 'config_dirs' directive. Also check NGINX Instance Manager web interface configuration if that component is in use.
    Affected if The config_dirs directive is present and configured in the NGINX Agent or NGINX Instance Manager configuration
  3. Verify config_dirs path boundaries
    Review the directory paths specified in the config_dirs directive. Identify if the configured paths allow access to sensitive system directories or if they are properly scoped to specific application directories only.
    Affected if The config_dirs directive points to directories that should not be accessible (such as /, /etc/, /root/, or any directory outside the intended secure scope)
  4. Confirm NGINX Instance Manager exposure
    Determine if NGINX Instance Manager is running and accessible. Check for nginx-instance-manager service (systemctl status nginx-instance-manager) and its configuration files in /etc/nginx-instance-manager/ or similar locations.
    Affected if NGINX Instance Manager is deployed and config_dirs can be configured through its web UI or API
  5. Review authentication and access controls
    Audit user accounts and API keys with access to NGINX Agent configuration or NGINX Instance Manager. Check for low-privileged accounts that have permission to modify or view the config_dirs setting.
    Affected if Low-privileged or unauthenticated users have the ability to modify the config_dirs configuration

Your environment is affected if NGINX Agent with a configurable config_dirs directive is running and the configured directories allow access outside the intended secure scope, especially if NGINX Instance Manager is accessible to low-privileged users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 2.22.2 / 2.46.7 or later
Fixed in 2.22.22.46.7
Interim mitigation

Restrict the config_dirs directive to only the minimum required directories, implement strict path validation (canonicalization and boundary checking), and ensure least-privilege access controls for NGINX Agent and Instance Manager authentication.

Fix this in Nginx Agent Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-60062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-60062 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data