Bugsink is vulnerable to Path Traversal attacks via event_id in ingestion
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bugsink | bugsink | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Bugsink | Bugsink | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-23153 | Bugsink path traversal via event_id in ingestion |
Github GHSA |
GHSA-q78p-g86f-jg6q | Bugsink path traversal via event_id in ingestion |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.658% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Bugsink
Bugsink bugsink |
|
| Vendors & Products |
Bugsink
Bugsink bugsink |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Bugsink is a self-hosted error tracking service. In versions 1.4.2 and below, 1.5.0 through 1.5.4, 1.6.0 through 1.6.3, and 1.7.0 through 1.7.3, ingestion paths construct file locations directly from untrusted event_id input without validation. A specially crafted event_id can result in paths outside the intended directory, potentially allowing file overwrite or creation in arbitrary locations. Submitting such input requires access to a valid DSN, potentially exposing them. If Bugsink runs in a container, the effect is confined to the container’s filesystem. In non-containerized setups, the overwrite may affect other parts of the system accessible to that user. This is fixed in versions 1.4.3, 1.5.5, 1.6.4 and 1.7.4. | |
| Title | Bugsink is vulnerable to Path Traversal attacks via event_id in ingestion | |
| Weaknesses | CWE-22 | |
| References |
|
|
| Metrics |
cvssV4_0
|