Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

OneUptime WhatsApp Webhook Missing Signature Verification

CVE-2026-33143GHSA-g5ph-f57v-mwjc

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (oneuptime 10.0.34), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm oneuptime

    Affected
    < 10.0.34
    Fixed in
    10.0.34

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-33143: 0.18% estimated exploitation activity in the next 30 days; percentile 8.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The WhatsApp POST webhook handler (/notification/whatsapp/webhook) processes incoming status update events without verifying the Meta/WhatsApp X-Hub-Signature-256 HMAC signature, allowing any unauthenticated attacker to send forged webhook payloads that manipulate notification delivery status records, suppress alerts, and corrupt audit trails. The codebase already implements proper signature verification for Slack webhooks. Details Vulnerable code — App/FeatureSet/Notification/API/WhatsApp.ts lines 372-430: Compare with the Slack webhook which correctly validates signatures: Common/Server/Middleware/SlackAuthorization.ts line 58: The WhatsApp GET webhook correctly validates the verify token — only the POST handler (which processes actual events) is missing signature verification. No existing CVEs cover webhook signature verification issues in OneUptime. The closest is GHSA-cw6x-mw64-q6pv (WhatsApp Resend Verification Auth Bypass), which is about a different WhatsApp-related…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-g5ph-f57v-mwjc

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-g5ph-f57v-mwjc

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33143

Advisory: OneUptime WhatsApp Webhook Missing Signature Verification
IDs: CVE-2026-33143, GHSA-g5ph-f57v-mwjc
Record: https://patchnext.com/advisories/cve-2026-33143 (revision 3, source checked 26 Oct 2026, 12:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: oneuptime 10.0.34. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm oneuptime: affected < 10.0.34; fixed in 10.0.34

## Suggested inspection (read-only)
- `npm ls oneuptime --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on oneuptime.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-g5ph-f57v-mwjc (OSV record GHSA-g5ph-f57v-mwjc lists affected ranges: npm oneuptime >=0 <10.0.34 (fixed))
- Verified: https://github.com/advisories/GHSA-g5ph-f57v-mwjc (GitHub-reviewed advisory GHSA-g5ph-f57v-mwjc lists affected ranges: npm oneuptime >=0 <10.0.34)

Commands are suggestions: review each one before running it.

Loading voting…