dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-46724

MEDIUM · 5.9 CVSS v4.0 Published 2026-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable 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
The file indexer does not normalize the configured directory path. A backend user with permission to edit indexer configurations can index documents from arbitrary locations on the server file system through path traversal sequences.

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 · high confidence

The file indexer lacks proper path normalization, allowing authenticated backend users with indexer configuration permissions to use path traversal sequences (e.g., ../../) to access files outside the intended directory.

MitigationImplement path normalization and validation to ensure the resolved path stays within the configured directory bounds, rejecting any traversal sequences that escape the intended scope.

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
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 if the file indexer component is installed
    Locate the file indexer module in your application (check for indexer-related binaries, services, or web endpoints). Look for configuration files named indexer.conf, indexer.yaml, or similar in your application directory.
    Affected if The file indexer component exists in your environment and is actively running or loadable.
  2. Verify if any user roles have indexer configuration permissions
    Review your user role definitions and permission matrices. Check for permissions labeled as 'indexer configuration', 'configure indexer', or similar. Inspect the authentication backend for role-permission assignments.
    Affected if Authenticated backend users are assigned roles that include indexer configuration permissions.
  3. Inspect the indexer's base directory configuration
    Examine the indexer configuration file or database settings for the configured base/target directory that the indexer is supposed to operate within. Look for parameters like 'base_path', 'index_directory', or 'root_dir'.
    Affected if A base directory is configured and the indexer has access to file system paths.
  4. Check for path normalization or validation logic in indexer code
    Review the indexer source code or binary for path handling functions. Search for path traversal sequence handling (../ patterns) or path resolution functions like realpath(), normalize(), or path.resolve(). Inspect whether the indexer validates that resolved paths remain within the configured base directory.
    Affected if No path normalization or boundary validation is implemented before processing file paths.
  5. Test path traversal behavior if indexer is configurable
    If you have indexer configuration access, configure the indexer to process a path containing traversal sequences (e.g., ../../etc/) and observe whether files outside the intended base directory are accessible or indexed.
    Affected if Path traversal sequences are accepted and the indexer accesses files outside the configured base directory.

Your environment is affected if the file indexer component is installed, users with indexer configuration permissions exist, and the indexer lacks path normalization to prevent traversal sequences from escaping the configured directory bounds.

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 path normalization and validation to ensure the resolved path stays within the configured directory bounds, rejecting any traversal sequences that escape the intended scope.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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