dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-7784

HIGH · 7.3 CVSS v3.1 Published 2026-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
A vulnerability has been found in RTGS2017 NagaAgent up to 5.1.0. This issue affects some unknown processing of the file apiserver/routes/extensions.py of the component Skills Endpoint. Such manipulation of the argument Name leads to path traversal. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

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

A path traversal vulnerability exists in the NagaAgent Skills Endpoint (apiserver/routes/extensions.py). The 'Name' parameter is not properly validated, allowing attackers to use directory traversal sequences (e.g., ../../../) to access arbitrary files on the server filesystem. This is a remote, network-exploitable vulnerability affecting versions up to 5.1.0.

MitigationImplement strict input validation on the Name parameter using an allowlist approach, sanitize path traversal sequences, and use secure path resolution methods (e.g., os.path.realpath) to ensure accessed files remain within intended directories.

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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 NagaAgent installation and version
    Locate the NagaAgent installation directory and check the version file or use a version command if available. Common locations may include /opt/nagaagent, /usr/local/nagaagent, or a service-installed path. Compare the found version against the affected range (versions up to 5.1.0).
    Affected if The installed version is 5.1.0 or any earlier version.
  2. Locate the affected source file
    Search for the file apiserver/routes/extensions.py within the NagaAgent installation directory. This file contains the vulnerable Skills Endpoint code.
    Affected if The file apiserver/routes/extensions.py exists in the installation, indicating the vulnerable code is present.
  3. Verify the API server is running
    Check if the NagaAgent API server process is active. This may be done via process listing (ps aux | grep nagaagent), service status commands, or checking if the API port is listening (commonly ports 8080, 8000, or a configured port).
    Affected if The API server is running and accepting connections.
  4. Confirm Skills Endpoint is accessible
    Attempt to access the Skills Endpoint (typically /api/skills or /extensions/skills) on the running API server. This can be done with a curl or HTTP request to the endpoint, with special attention to whether the Name parameter is accepted.
    Affected if The Skills Endpoint responds to HTTP requests and accepts a Name parameter.
  5. Test for path traversal vulnerability
    If authorized in your testing environment, send a request to the Skills Endpoint with a Name parameter containing directory traversal sequences (e.g., ../../../etc/passwd or ../../../windows/win.ini). Observe if the response returns file contents from outside the intended directory.
    Affected if The Name parameter allows traversal sequences and returns content from arbitrary file paths.

You are affected if NagaAgent version 5.1.0 or earlier is installed, the API server is running, and the Skills Endpoint with its Name parameter is accessible and accepts path traversal sequences.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on the Name parameter using an allowlist approach, sanitize path traversal sequences, and use secure path resolution methods (e.g., os.path.realpath) to ensure accessed files remain within intended directories.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7784 — 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-7784 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