Insecure Inherited Permissions in neoan3-apps/template

Exploitation

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

CVSS

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

EPSS

• CVE-2021-41170: 1.58% estimated exploitation activity in the next 30 days; percentile 75.57 (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.

Impact Versions prior 1.1.1 have allowed for passing in closures directly into the template engine. As a result values that are callable are executed by the template engine. The issue arises if a value has the same name as a method or function in scope and can therefore be executed either by mistake or maliciously. In theory all users of the package are affected as long as they either deal with direct user input or database values. A multi-step attack on is therefore plausible. Patches Version 1.1.1 has addressed this vulnerability. Workarounds Unfortunately only working with hardcoded values is safe in prior versions. As this likely defeats the purpose of a template engine, please upgrade. References As a possible exploit is relatively easy to achieve, I will not share steps to reproduce the issue for now. For more information If you have any questions or comments about this advisory: Open an issue in our repo

Published by the source

10 Nov 2021, 16:41 UTC

Last modified by the source

1 Feb 2023, 05:06 UTC

Source last checked

26 Oct 2026, 14:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3v56-q6r6-4gcw

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

# Patch Next advisory brief: CVE-2021-41170

Advisory: Insecure Inherited Permissions in neoan3-apps/template
IDs: CVE-2021-41170, GHSA-3v56-q6r6-4gcw
Record: https://patchnext.com/advisories/cve-2021-41170 (revision 1, source checked 26 Oct 2026, 14:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: neoan3-apps/template 1.1.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist neoan3-apps/template: affected < 1.1.1; fixed in 1.1.1

## Suggested inspection (read-only)
- Packagist neoan3-apps/template: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on neoan3-apps/template.
- 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://github.com/advisories/GHSA-3v56-q6r6-4gcw (GitHub-reviewed advisory GHSA-3v56-q6r6-4gcw lists affected ranges: Packagist neoan3-apps/template >=0 <1.1.1)

Commands are suggestions: review each one before running it.