dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-5557

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
A vulnerability was detected in badlogic pi-mono up to 0.58.4. This issue affects some unknown processing of the file packages/mom/src/slack.ts of the component pi-mom Slack Bot. The manipulation results in authentication bypass using alternate channel. The attack can be executed remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 · moderate confidence

Authentication bypass vulnerability in the pi-mono Slack Bot (packages/mom/src/slack.ts) allowing remote attackers to bypass authentication through an alternate channel. The vulnerability exists in versions up to 0.58.4 and a public exploit is available.

MitigationSince the vendor did not respond, internally review the authentication logic in slack.ts to identify the alternate channel bypass vector. Implement proper authentication validation, consider updating to any available patched version, and restrict Slack API permissions to least privilege.

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

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 pi-mono version
    Locate the package.json file in the pi-mono root directory and read the 'version' field, or run 'npm list pi-mono' or 'npm list mom' if installed as a dependency
    Affected if the installed version is 0.58.4 or earlier
  2. Verify mom Slack Bot component is present
    Check for the existence of the packages/mom directory in the pi-mono installation, or verify the 'mom' package is listed in dependencies
    Affected if the packages/mom directory or mom package dependency exists
  3. Confirm vulnerable slack.ts file exists
    Inspect the file packages/mom/src/slack.ts for the presence of authentication logic that can be bypassed via an alternate channel
    Affected if the slack.ts file exists and contains Slack Bot authentication code
  4. Check Slack Bot configuration for alternate channel exposure
    Review configuration files (such as .env, config.json, or slack-config) for settings that enable or expose the Slack Bot component to network access or alternate communication channels
    Affected if the Slack Bot is exposed to network access or alternate channels without proper authentication guards
  5. Audit Slack Bot authentication implementation
    Examine the authentication mechanism in slack.ts to determine if it relies solely on channel-based validation without additional verification
    Affected if authentication depends only on channel membership without supplementary identity verification

You are affected if pi-mono version is 0.58.4 or earlier AND the mom Slack Bot component is installed and accessible.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the vendor did not respond, internally review the authentication logic in slack.ts to identify the alternate channel bypass vector. Implement proper authentication validation, consider updating to any available patched version, and restrict Slack API permissions to least privilege.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5557 — 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-5557 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