Which versions of gregwar/rst are affected by GHSA-2GQ2-M628-33XP?

gregwar/rst (composer) versions < 1.0.3 is affected.

Is there a fix for GHSA-2GQ2-M628-33XP?

Yes. GHSA-2GQ2-M628-33XP is fixed in 1.0.3. Upgrade to this version or later.

Is GHSA-2GQ2-M628-33XP exploitable, and should I be worried?

Whether GHSA-2GQ2-M628-33XP is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-2GQ2-M628-33XP is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-2GQ2-M628-33XP in gregwar/rst

Q: What is GHSA-2GQ2-M628-33XP?

GHSA-2GQ2-M628-33XP is a high-severity security vulnerability in gregwar/rst (composer), affecting versions < 1.0.3. It is fixed in 1.0.3.

Q: Is there a fix for GHSA-2GQ2-M628-33XP?

Yes. GHSA-2GQ2-M628-33XP is fixed in 1.0.3. Upgrade to this version or later.

Q: Is GHSA-2GQ2-M628-33XP exploitable, and should I be worried?

Whether GHSA-2GQ2-M628-33XP is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-2GQ2-M628-33XP is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-2GQ2-M628-33XP?

Upgrade gregwar/rst to 1.0.3 or later.

GHSA-2GQ2-M628-33XP

GHSA-2GQ2-M628-33XP is a high-severity security vulnerability in gregwar/rst (composer), affecting versions < 1.0.3. It is fixed in 1.0.3.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

gregwar/rst Local File Inclusion Vulnerability

A Local File Inclusion (LFI) vulnerability has been discovered in the gregwar/rst library, potentially exposing sensitive files on the server to unauthorized users. The issue arises from inadequate input validation, allowing an attacker to manipulate file paths and include arbitrary files.

Impact

Affected versions

gregwar/rst (< 1.0.3)

Security releases

gregwar/rst → 1.0.3 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade gregwar/rst to 1.0.3 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-2GQ2-M628-33XP? GHSA-2GQ2-M628-33XP is a high-severity security vulnerability in gregwar/rst (composer), affecting versions < 1.0.3. It is fixed in 1.0.3.
Which versions of gregwar/rst are affected by GHSA-2GQ2-M628-33XP? gregwar/rst (composer) versions < 1.0.3 is affected.
Is there a fix for GHSA-2GQ2-M628-33XP? Yes. GHSA-2GQ2-M628-33XP is fixed in 1.0.3. Upgrade to this version or later.
Is GHSA-2GQ2-M628-33XP exploitable, and should I be worried? Whether GHSA-2GQ2-M628-33XP is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-2GQ2-M628-33XP is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-2GQ2-M628-33XP? Upgrade gregwar/rst to 1.0.3 or later.