How severe is GHSA-634p-93h9-92vh?

GHSA-634p-93h9-92vh has a CVSS score of 5.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-634p-93h9-92vh?

GHSA-634p-93h9-92vh affects the following packages: some-natalie/ghas-to-csv (GitHub Actions). Ecosystems affected: GitHub Actions.

How do I fix GHSA-634p-93h9-92vh?

Update some-natalie/ghas-to-csv to 1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-634p-93h9-92vh is resolved across your whole dependency graph.

How do I detect GHSA-634p-93h9-92vh in my GitHub Actions dependencies?

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

How do I mitigate GHSA-634p-93h9-92vh 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.

Is GHSA-634p-93h9-92vh actively exploited in the wild?

No public exploit code has been indexed for GHSA-634p-93h9-92vh 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-634p-93h9-92vh?

GHSA-634p-93h9-92vh has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 48th 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.

What type of vulnerability is GHSA-634p-93h9-92vh?

GHSA-634p-93h9-92vh is classified as CWE-74 (CWE-74). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-634p-93h9-92vh published, and has it been updated?

GHSA-634p-93h9-92vh was published on September 16, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 GitHub Actions

Not in CISA KEV

MEDIUM severity

ghas-to-csv vulnerable to Improper Neutralization of Formula Elements in a CSV FileGHSA-634p-93h9-92vh

MEDIUMFix: some-natalie/ghas-to-csv#20

GHSA-634p-93h9-92vh is a medium-severity (CVSS 5.8) CWE-74 vulnerability in some-natalie/ghas-to-csv. A fix is available for some-natalie/ghas-to-csv — see the affected versions and patch details below.

Also known asCVE-2022-39217

Published

Sep 16, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-634p-93h9-92vh.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

📦some-natalie/ghas-to-csv

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

Description

Impact

This GitHub Action creates a CSV file without sanitizing the output of the APIs. If an alert is dismissed or any other custom field contains executable code / formulas, it might be run when an endpoint opens that CSV file in a spreadsheet program. The data flow looks like this 👇🏻

graph TD
    A(Repository) -->|developer dismissal, other data input| B(GitHub Advanced Security data)
    B -->|ghas-to-csv| C(CSV file)
    C -->|spreadsheet program| D(endpoint executes potentially malicious code)

Patches

Please use version v1 or later. That tag moves from using csv to defusedcsv to mitigate this problem.

Workarounds

There is no workaround. Please upgrade to using the latest tag, v1 (or later).

References

CWE-1236 information from MITRE
CSV injection information from OWASP
CodeQL query for CWE-1236 in Python here
PyPI site for defusedcsv here

For more information

If you have any questions or comments about this advisory:

Open an issue in this repository here

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦GitHub Actions	`some-natalie/ghas-to-csv`	all versions	1

Affected Products

1 product · 1 configurations

Application

ghas-to-csvghas-to-csv_project

< 1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for some-natalie/ghas-to-csv, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update some-natalie/ghas-to-csv to 1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-634p-93h9-92vh 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.

Frequently Asked Questions

### Impact This GitHub Action creates a CSV file without sanitizing the output of the APIs. If an alert is dismissed or any other custom field contains executable code / formulas, it might be run when an endpoint opens that CSV file in a spreadsheet program. The data flow looks like this 👇🏻 ```mermaid graph TD A(Repository) -->|developer dismissal, other data input| B(GitHub Advanced Security data) B -->|ghas-to-csv| C(CSV file) C -->|spreadsheet program| D(endpoint executes potentially malicious code) ``` ### Patches Please use version `v1` or later. That tag moves from