How severe is GHSA-jq43-q8mx-r7mq?

GHSA-jq43-q8mx-r7mq has a CVSS score of 7.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jq43-q8mx-r7mq?

GHSA-jq43-q8mx-r7mq affects the following packages: github.com/migueldeicaza/SwiftTerm (SwiftURL). Ecosystems affected: SwiftURL.

How do I fix GHSA-jq43-q8mx-r7mq?

Update github.com/migueldeicaza/SwiftTerm to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jq43-q8mx-r7mq is resolved across your whole dependency graph.

How do I detect GHSA-jq43-q8mx-r7mq in my SwiftURL dependencies?

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

How do I mitigate GHSA-jq43-q8mx-r7mq if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-jq43-q8mx-r7mq actively exploited in the wild?

No public exploit code has been indexed for GHSA-jq43-q8mx-r7mq 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-jq43-q8mx-r7mq?

GHSA-jq43-q8mx-r7mq has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 39th 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-jq43-q8mx-r7mq?

GHSA-jq43-q8mx-r7mq is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-jq43-q8mx-r7mq published, and has it been updated?

GHSA-jq43-q8mx-r7mq was published on July 14, 2023 and was last updated on February 9, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 SwiftURL

Not in CISA KEV

HIGH severity

SwiftTerm Code Injection vulnerabilityGHSA-jq43-q8mx-r7mq

HIGHFix: migueldeicaza/SwiftTerm@a94e6b2

GHSA-jq43-q8mx-r7mq is a high-severity (CVSS 7.1) Code Injection vulnerability in github.com/migueldeicaza/SwiftTerm. A fix is available for github.com/migueldeicaza/SwiftTerm — see the affected versions and patch details below.

Also known asCVE-2022-23465

Published

Jul 14, 2023

Updated

Feb 9, 2024

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-jq43-q8mx-r7mq.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs39th percentile — riskier than 39% 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

📦github.com/migueldeicaza/SwiftTerm

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

Description

Impact

Attacker could modify the window title via a certain character escape sequence and then insert it back to the command line in the user's terminal, e.g. when the user views a file containing the malicious sequence, which could allow the attacker to execute arbitrary commands.

Credit

These bugs were found and disclosed by David Leadbeater [email protected] (@dgl at Github.com)

Patches

Fixed in version ce596e0dc8cdb288bc7ed5c6a59011ee3a8dc171

Workarounds

There are no workarounds available

References

Similar exploits to this existed in the past, for terminal emulators:

https://nvd.nist.gov/vuln/detail/CVE-2003-0063 https://nvd.nist.gov/vuln/detail/CVE-2008-2383

Additional background and information is also available:

https://marc.info/?l=bugtraq&m=104612710031920&w=2 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510030

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦SwiftURL	`github.com/migueldeicaza/SwiftTerm`	all versions	1.2.0

Affected Products

1 product · 1 configurations

Application

swifttermswiftterm_project

< 2022-12-02

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/migueldeicaza/SwiftTerm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/migueldeicaza/SwiftTerm to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jq43-q8mx-r7mq is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### Impact Attacker could modify the window title via a certain character escape sequence and then insert it back to the command line in the user's terminal, e.g. when the user views a file containing the malicious sequence, which could allow the attacker to execute arbitrary commands. ### Credit These bugs were found and disclosed by David Leadbeater <[email protected]> (@dgl at Github.com) ### Patches Fixed in version ce596e0dc8cdb288bc7ed5c6a59011ee3a8dc171 ### Workarounds There are no workarounds available ### References Similar exploits to this existed in the past, for terminal emulators