Advisory record · GHSA-6m9f-8vwq-97pm

Smarty Does Not Consider Umask Values When Setting Permissions

No CVSS scoreEPSS 0.016 · 75th percentile

Published by the GitHub Advisory Database at 2 May 2022, 04:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
smarty/smartyPackagist<3.0.0-beta43.0.0-beta4
Identifiers
GHSA-6m9f-8vwq-97pm · CVE-2009-5054 · PKSA-54c6-f9b9-7wg4
Weakness (CWE)
CWE-281
Published
2 May 2022
Updated
4 Dec 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Smarty versions before 3.0.0-beta4 do not apply the umask when setting file permissions. The source gives few details on how an attacker would reach the files, but it says this could let them bypass intended access restrictions through standard filesystem operations. Upgrade smarty/smarty to 3.0.0-beta4 or later; no workaround is listed.

Written 4 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS 0.016, the 75th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:28 UTC First seen by agentprime
  2. 31 Oct 2026, 14:28 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.