Lack of validation for user-provided fields in GitForge.jl
Published Jun 25, 2025 · Updated Oct 23, 2026 · Also known as GHSA-g2xx-229f-3qjm, JLSEC-2025-3
Original summary
Normalized public record · Updated Oct 23, 2026
Lack of validation for user-provided fields in GitForge.jl
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
There is a lack of input validation for user-provided values in certain functions.
Potential impact
This means a user can add path traversal patterns like ../ in the input to access any other endpoints on api.github.com that were not intended.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- GHSA-g2xx-229f-3qjm, JLSEC-2025-3
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Jun 25, 2025 · Last refreshed Oct 23, 2026