CVE-2026-15392
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 · uneditedDBD::File versions before 1.651 for Perl do not ensure the table file is not a symlink to an untrusted location. The complete_table_name method builds the absolute table file path without checking whether the file is a symbolic link. A link inside the data directory can point to a table file at any path outside of the configured f_dir and f_dir_search directories. Callers of file-based drivers can read or write files outside of the data directory.
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 confidenceDBD::File versions before 1.651 have a symlink traversal vulnerability in the complete_table_name method. When building the absolute path for table files, the code does not check whether the file is a symbolic link, allowing attackers to create symlinks inside the data directory that point to files outside the configured f_dir and f_dir_search directories, enabling unauthorized read/write access to arbitrary filesystem locations.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed DBD::File versionRun `perl -MDBD::File -e 'print $DBD::File::VERSION . "\n"'` or check your Perl library directory for DBD::File version fileAffected if Version is lower than 1.651 or the version cannot be determined (module may be outdated)
-
Identify data directories used by DBD::FileSearch your application code for f_dir and f_dir_search parameters passed to DBD::File->new() or used in data_source strings (dbi:File:f_dir=...)Affected if f_dir or f_dir_search directories are used and contain user-writable content
-
Scan for symlinks in configured data directoriesRun `find /path/to/f_dir -type l -ls` and `find /path/to/f_dir_search -type l -ls` on each configured directoryAffected if Symbolic links exist inside the data directories pointing to locations outside the intended directories
-
Verify symlink targets are within expected boundariesFor each symlink found, use `readlink -f /path/to/symlink` to resolve the final target and confirm it stays within f_dir or f_dir_search treesAffected if Any symlink resolves to a path outside the configured f_dir or f_dir_search directories
You are affected if DBD::File version is below 1.651 AND your configured f_dir/f_dir_search directories contain symlinks that point outside those directories, allowing potential traversal.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpgrade DBD::File to version 1.651 or later which includes symlink validation. If upgrade is not immediately possible, ensure table file directories do not contain untrusted symlinks and consider restricting file permissions on the data directories.
DBD::File 1.651
- Check current DBD::File version using: perl -MDBD::File -e 'print $DBD::File::VERSION'
- Upgrade DBD::File to version 1.651 or later using: cpan DBD::File or cpanm DBD::File
- Verify the upgrade was successful by checking the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15392 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15392 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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