Is CVE-2026-40162 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-40162 being exploited in the wild.

How severe is CVE-2026-40162?

High severity, with a CVSS score of 7.1, published 10 April 2026.

Which products and versions are affected?

Bugsink 2.1.0; bugsink (PyPI) ECOSYSTEM:introduced=2.1.0,fixed=2.1.1.

Is there a fix for CVE-2026-40162?

Yes. bugsink (PyPI): upgrade to 2.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-40162 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-40162?

Check whether you run Bugsink or bugsink (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-40162: Bugsink authenticated arbitrary file write in artifact bundle assembly

CVE-2026-40162 · Severity: high · CVSS 7.1 · Published 2026-04-10

Bugsink, an error-tracking and log aggregation tool, contains a vulnerability that allows logged-in users to write or overwrite files on the server. An attacker with valid credentials could use this to corrupt application data, modify uploaded assets, or disrupt the service's normal operations. This issue is limited to the specific permissions granted to the Bugsink service account on the host system.

Technologies: Bugsink, bugsink (PyPI). Vendors: Bugsink, PyPI.

Quick answers

Is CVE-2026-40162 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-40162 being exploited in the wild.
How severe is CVE-2026-40162?: High severity, with a CVSS score of 7.1, published 10 April 2026.
Which products and versions are affected?: Bugsink 2.1.0; bugsink (PyPI) ECOSYSTEM:introduced=2.1.0,fixed=2.1.1.
Is there a fix for CVE-2026-40162?: Yes. bugsink (PyPI): upgrade to 2.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-40162 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-40162?: Check whether you run Bugsink or bugsink (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

bugsink (PyPI): upgrade to 2.1.1 or later
```
pip install "bugsink>=2.1.1"
```

Technical details

An authenticated arbitrary file write vulnerability exists in Bugsink version 2.1.0 within the 'artifactbundle/assemble' flow. The root cause is improper input validation (CWE-20) during the assembly of artifact bundles, which allows a user with a valid authentication token to specify filesystem locations for file writes. An attacker can create or overwrite any file that the Bugsink service account has write access to. While direct remote code execution has not been demonstrated, the impact includes data corruption and service disruption. The vulnerability is fixed in version 2.1.1.

Affected products

bugsink bugsink 2.1.0

Identifiers

CVE-2026-40162
GHSA-8hw4-fhww-273g
PYSEC-2026-2404

Timeline

2026-04-09: disclosed: Vulnerability published by the maintainer.
2026-04-10: advisory: GitHub Advisory and NVD entry published.
2026-04-10: patched: Version 2.1.1 released to address the issue.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.