dbcve.org
BugsinkApplication

CVE-2026-40162

HIGH · 7.1 CVSS v3.1 Published 2026-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Bugsink is a self-hosted error tracking tool. In 2.1.0, an authenticated file write vulnerability was identified in Bugsink 2.1.0 in the artifact bundle assembly flow. A user with a valid authentication token could cause the application to write attacker-controlled content to a filesystem location writable by the Bugsink process. This vulnerability is fixed in 2.1.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Bugsink 2.1.0 contains an authenticated file write vulnerability in the artifact bundle assembly flow. An attacker with a valid authentication token can write attacker-controlled content to any filesystem location writable by the Bugsink process.

MitigationUpgrade to Bugsink version 2.1.1 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BugsinkApplication
Affected:= 2.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Bugsink version
    Run the command: bugsink --version or check the application startup logs for the version number
    Affected if The version displayed is exactly 2.1.0
  2. Locate the Bugsink configuration file
    Look for bugsink.conf or config.py in the Bugsink installation directory, commonly found in /etc/bugsink/, /opt/bugsink/config/, or the application's root directory
    Affected if The configuration file exists and the application is running version 2.1.0
  3. Verify if artifact bundle assembly is enabled
    Search the configuration file for settings related to 'artifact', 'bundle', 'upload', or 'assembly' features. Check for any enabled flags or module configurations for these features
    Affected if Artifact bundle assembly is explicitly enabled in the configuration
  4. Check authentication configuration
    Inspect the authentication settings in the configuration file, looking for auth token settings, API key configuration, or user authentication method definitions
    Affected if External or token-based authentication is configured, allowing valid auth tokens to be used for API access
  5. Identify filesystem permissions on the Bugsink process
    Run: ps aux | grep bugsink to find the process user, then check which directories that user has write access to using: ls -la on common writable paths like /tmp, /var/tmp, or application data directories
    Affected if The Bugsink process runs with write access to sensitive filesystem locations beyond intended artifact storage directories

You are affected if the installed Bugsink version is exactly 2.1.0 and the artifact bundle assembly feature is enabled with valid authentication tokens permitted for access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Bugsink version 2.1.1 or later to remediate this vulnerability.

Recommended fix High confidence

2.1.1

  1. Upgrade Bugsink from version 2.1.0 to version 2.1.1
  2. Verify the upgrade was successful by checking the installed version
  3. Ensure the application is running correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bugsink Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40162 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40162 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data