CVE-2026-44225
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 · uneditedPulpy is a lightweight, cross-platform desktop application packager for web apps. Prior to 0.1.1, Pulpy injects a pulpy.fs JavaScript API into every packaged web application, giving it access to the host filesystem. A validateFsPath() function is supposed to sandbox this access, but its blocklist is incomplete. Any web app packaged with Pulpy can read and write arbitrary files in the user's home directory — including ~/.ssh/id_rsa, ~/.aws/credentials, and ~/Library/Keychains/. This vulnerability is fixed in 0.1.1.
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 confidencePulpy prior to 0.1.1 injects a pulpy.fs JavaScript API providing filesystem access to packaged web apps. The validateFsPath() function's incomplete blocklist allows reading/writing arbitrary files in the user's home directory, including sensitive files like ~/.ssh/id_rsa, ~/.aws/credentials, and Keychain data.
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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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.
-
Identify Pulpy installation and versionRun 'npm list pulpy' or check package.json dependencies for pulpy version entryAffected if Pulpy version is present and less than 0.1.1
-
Locate packaged application using pulpy.fsSearch project files for 'pulpy.fs' import statements or require() calls, or inspect the packaged application bundle for pulpy.fs API usageAffected if The application code imports or uses the pulpy.fs module
-
Check if validateFsPath is in useInspect the packaged application or node_modules/pulpy for the validateFsPath function being called during file operationsAffected if File operations via pulpy.fs are performed in the packaged app
-
Verify sensitive file exposureTest reading a sensitive file path like ~/.ssh/id_rsa through the pulpy.fs API if accessible, or review application logs for blocklist bypass attemptsAffected if The home directory files are accessible through the API despite blocklist protection
You are affected if you use Pulpy versions prior to 0.1.1 in a packaged web application that utilizes the pulpy.fs API to access filesystem paths.
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 Pulpy to version 0.1.1 where the blocklist is fixed, and rebuild/re-package any applications using the vulnerable version.
Pulpy version 0.1.1
- Identify the currently installed version of Pulpy by checking the application's version information or package manager
- Download Pulpy version 0.1.1 or later from the official GitHub repository or release channel
- Replace the existing Pulpy installation with version 0.1.1
- Restart any running Pulpy instances to ensure the new version is active
- Repackage any existing web applications using the updated Pulpy to ensure they benefit from the fixed validateFsPath() function
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44225 — 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-44225 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