CVE-2019-5437: Unauthorized File Access in harp

harp Updated 02 Oct 2025

Summary

13/06/2019
Yes i
Moderate
5.3

CVE-2019-5437: Unauthorized File Access in harp. Affects harp versions < 0.40.2. Fixed in 0.40.2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The harp package is an npm package used for static site generation. It allows users to build and serve static websites with ease. However, versions of harp prior to 0.40.2 are vulnerable to Unauthorized File Access. The package incorrectly ignores files and directories with names that start with an underscore, such as _secret-folder. If the underscore character is URL encoded, the server delivers the file, potentially exposing sensitive information.

Vulnerability Detail

The vulnerability in harp allows an attacker to access files that should be protected. By URL encoding the underscore character, an attacker can bypass the package's file exclusion mechanism and retrieve files that were intended to be hidden. This can lead to unauthorized access to sensitive information, such as configuration files, credentials, or other confidential data. The impact of this vulnerability depends on the nature of the exposed files and the permissions of the user running the harp server.

How To Fix

Latest published version: 0.50.1 as of 22 Oct 2026

npm install harp@0.50.1

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.40.2

This is the first release that contains the fix.

npm install harp@0.40.2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. Upgrading to the fixed version is the recommended solution.

Conclusion

In conclusion, the harp package versions prior to 0.40.2 are vulnerable to Unauthorized File Access. It is crucial to upgrade to version 0.40.2 or later to mitigate this vulnerability and prevent unauthorized access to sensitive files. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for harp →

Share this vulnerability

FAQ

This vulnerability allows an attacker to access files that should be protected, potentially exposing sensitive information.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your package-lock.json file and the playground will analyze it for vulnerabilities in real-time.

No, only versions of harp prior to 0.40.2 are affected. Upgrading to version 0.40.2 or later will fix the vulnerability.

No, there is no known workaround for this vulnerability. Upgrading to the fixed version is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for harp.

How To Fix

Latest published version: 0.50.1 as of 22 Oct 2026

npm install harp@0.50.1

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.40.2

This is the first release that contains the fix.

npm install harp@0.40.2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback