How severe is GHSA-c7j7-p5jq-26ff?

No CVSS score has been assigned to GHSA-c7j7-p5jq-26ff yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c7j7-p5jq-26ff?

GHSA-c7j7-p5jq-26ff affects the following packages: passenger (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-c7j7-p5jq-26ff?

Update passenger to 4.0.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c7j7-p5jq-26ff is resolved across your whole dependency graph.

How do I detect GHSA-c7j7-p5jq-26ff in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for passenger, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-c7j7-p5jq-26ff 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 GHSA-c7j7-p5jq-26ff?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-c7j7-p5jq-26ff can be triaged on real exposure rather than presence alone.

Is GHSA-c7j7-p5jq-26ff actively exploited in the wild?

No public exploit code has been indexed for GHSA-c7j7-p5jq-26ff 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 is the EPSS score for GHSA-c7j7-p5jq-26ff?

GHSA-c7j7-p5jq-26ff has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-c7j7-p5jq-26ff published, and has it been updated?

GHSA-c7j7-p5jq-26ff was published on October 10, 2018 and was last updated on December 8, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

Not in CISA KEV

GHSA-c7j7-p5jq-26ff — passenger

Fix: phusion/passenger@34b1087

GHSA-c7j7-p5jq-26ff is a security vulnerability in passenger. A fix is available for passenger — see the affected versions and patch details below.

Insecure use of temporary files in passenger

Also known asCVE-2014-1831

Published

Oct 10, 2018

Updated

Dec 8, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

💎passenger

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

Description

Phusion Passenger before 4.0.38 allows local users to write to certain files and directories via a symlink attack on

control_process.pid or
a generation-* file.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`passenger`	all versions	4.0.38`bundle update passenger --conservative`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for passenger, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update passenger to 4.0.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c7j7-p5jq-26ff 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-c7j7-p5jq-26ff can be triaged on real exposure rather than presence alone.

Tailored to GHSA-c7j7-p5jq-26ff. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Phusion Passenger before 4.0.38 allows local users to write to certain files and directories via a symlink attack on 1. `control_process.pid` or 2. a generation-* file.

O3 Security · Impact-Aware SCA

Is GHSA-c7j7-p5jq-26ff in your dependencies?

O3 Security finds GHSA-c7j7-p5jq-26ff across RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works