How severe is CVE-2009-5054?

No CVSS score has been assigned to CVE-2009-5054 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2009-5054?

CVE-2009-5054 affects the following packages: smarty/smarty (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2009-5054?

Update smarty/smarty to 3.0.0-beta4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-5054 is resolved across your whole dependency graph.

How do I detect CVE-2009-5054 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for smarty/smarty. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2009-5054 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2009-5054?

O3 pinpoints whether CVE-2009-5054 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2009-5054 actively exploited in the wild?

No public exploit code has been indexed for CVE-2009-5054 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2009-5054?

CVE-2009-5054 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2009-5054 published, and has it been updated?

CVE-2009-5054 was published on February 3, 2011 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

CVE-2009-5054

CVE-2009-5054 is a CWE-264 vulnerability in smarty/smarty. O3 Security confirms whether CVE-2009-5054 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Smarty Does Not Consider Umask Values When Setting Permissions

Also known asGHSA-6m9f-8vwq-97pm

Published

Feb 3, 2011

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐘smarty/smarty

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Smarty before 3.0.0 beta 4 does not consider the umask value when setting the permissions of files, which might allow attackers to bypass intended access restrictions via standard filesystem operations.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`smarty/smarty`	all versions	3.0.0-beta4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for smarty/smarty. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update smarty/smarty to 3.0.0-beta4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-5054 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2009-5054 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2009-5054. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2009-5054 in your dependencies?

O3 detects CVE-2009-5054 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works