CVE-2026-9472
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 · uneditedA flaw has been found in dazeb markdown-downloader up to 3d4394b34b6c99d81af817623af55e3384df5a6a. Affected is the function download_markdown/list_downloaded_files/create_subdirectory of the file src/index.ts. Executing a manipulation can lead to path traversal. The attack can be launched remotely. The exploit has been published and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. 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 · high confidenceThe markdown-downloader project contains a path traversal vulnerability in the download_markdown/list_downloaded_files/create_subdirectory functions within src/index.ts. The vulnerability allows attackers to manipulate file paths to access directories outside the intended scope, potentially reading or writing sensitive files on the host system.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if dazeb markdown-downloader is installedSearch for the package in your environment using 'npm list dazeb' or 'pip show dazeb' or check your package.json/requirements.txt for this dependencyAffected if The dazeb markdown-downloader package is present in your project dependencies
-
Locate the affected source fileFind src/index.ts in the dazeb package directory - look in node_modules/dazeb/ or the project's node_modulesAffected if The file src/index.ts exists and contains the download_markdown, list_downloaded_files, or create_subdirectory functions
-
Inspect the create_subdirectory function for path validationOpen src/index.ts and examine the create_subdirectory function - look for path sanitization logic, path.normalize(), path.resolve() or similar validationAffected if The function lacks proper input sanitization and accepts user-controlled path parameters without validating they stay within intended boundaries
-
Verify if the vulnerable function receives external inputTrace how file paths reach create_subdirectory - check if query parameters, API requests, or user input flows directly to this function without validationAffected if Unvalidated path input from external sources (HTTP requests, CLI arguments, API calls) reaches the create_subdirectory function
You are affected if dazeb markdown-downloader is installed and user-supplied file paths can reach the create_subdirectory function without validation.
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.
From vendor dataImplement strict input validation and path sanitization using canonical path resolution (e.g., path.resolve()) combined with allowlist validation to ensure all file operations remain within intended directories. Additionally, reject any path containing traversal sequences like '..' or absolute paths.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9472 — 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-9472 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