Insecure template handling in express-hbs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N

EPSS

• CVE-2021-32817: 1.27% estimated exploitation activity in the next 30 days; percentile 69.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

express-hbs is an Express handlebars template engine. express-hbs mixes pure template data with engine configuration options through the Express render API. More specifically, the layout parameter may trigger file disclosure vulnerabilities in downstream applications. This potential vulnerability is somewhat restricted in that only files with existing extentions (i.e. file.extension) can be included, files that lack an extension will have .hbs appended to them. For complete details refer to the referenced GHSL-2021-019 report. Notes in documentation have been added to help users of express-hbs avoid this potential information exposure vulnerability.

Published by the source

17 May 2021, 20:58 UTC

Last modified by the source

6 Dec 2023, 01:01 UTC

Source last checked

26 Oct 2026, 12:21 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-rwxp-hwwf-653v

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-rwxp-hwwf-653v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-32817

Advisory: Insecure template handling in express-hbs
IDs: CVE-2021-32817, GHSA-rwxp-hwwf-653v
Record: https://patchnext.com/advisories/cve-2021-32817 (revision 2, source checked 26 Oct 2026, 12:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm express-hbs: affected <= 2.4.0

## Suggested inspection (read-only)
- `npm ls express-hbs --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on express-hbs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-rwxp-hwwf-653v (OSV record GHSA-rwxp-hwwf-653v lists affected ranges: npm express-hbs >=0 <=2.4.0)
- Verified: https://github.com/advisories/GHSA-rwxp-hwwf-653v (GitHub-reviewed advisory GHSA-rwxp-hwwf-653v lists affected ranges: npm express-hbs >=0 <=2.4.0)

Commands are suggestions: review each one before running it.