Vulnerability in GitForge (CVE-2025-50178)

Summary

Vulnerability in GitForge (CVE-2025-50178). Risk of unauthorized operations or information disclosure. Exploitable via owner. Mitigation: upgrade to 0.4.3 or later.

Original description

The description as published by the source.

Description

There is a lack of input validation for user-provided values in certain functions.

In the GitForge.get_repo() function for GitHub, the user can provide any string for the owner and repo fields. These inputs are not validated or safely encoded and are sent directly to the server.

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.

Patches

Users should upgrade immediately to v0.4.3. All prior versions are vulnerable.

Workarounds

None

References

Fixed by: https://github.com/JuliaWeb/GitForge.jl/pull/50 (which is available in v0.4.3).

Credits

Thanks to splitline from the DEVCORE Research Team for reporting this issue.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-50178 has been found in GitForge.
Attackers can target a specific entry point like owner over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade GitForge to 0.4.3 or later.
If unsure, ask your IT team or search "GitForge CVE-2025-50178" on the vendor's site.

CVE-2025-50178 (GitForge)
Attack surface: owner / api.github.com
Patched: 0.4.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in GitForge. Attackers reach the vulnerable code path via owner.

📍 Affected scope

Check the vendor advisory for the affected versions of GitForge. Attack surface: owner / api.github.com.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.4.3.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'GitForge' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'GitForge' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で GitForge を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade GitForge to 0.4.3
```
ステージング環境で 0.4.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Julia GitForge

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.4.3"}]}]

References

web github.com
web github.com