# CVE-2026-33143: OneUptime: WhatsApp Webhook Missing Signature Verification

> Attackers can forge WhatsApp webhook payloads to manipulate notification statuses and suppress alerts due to missing signature verification.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-g5ph-f57v-mwjc

## What is CVE-2026-33143?

CVE-2026-33143 is a high-severity missing authorization vulnerability in oneuptime, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OneUptime is a solution for monitoring and managing online services. Prior to version 10.0.34, 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. This issue has been patched in version 10.0.34.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-33143?

2 open source packages ship an affected version, including oneuptime. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `oneuptime` | npm | All versions | 10.0.34 |
| `oneuptime` | npm | All versions | 10.0.34 |

Products: Hackerbay Oneuptime.

## How do I fix CVE-2026-33143?

Upgrade oneuptime to 10.0.34 or later.

## Is CVE-2026-33143 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33143 exists.

## Other vulnerabilities in oneuptime

- [CVE-2026-33396](https://insights.sbomify.com/CVE-2026-33396/): Code injection in oneuptime (critical 10.0)
- [CVE-2026-32306](https://insights.sbomify.com/CVE-2026-32306/): OneUptime ClickHouse SQL Injection via Aggregate Query Parameters (critical 10.0)
- [CVE-2026-30956](https://insights.sbomify.com/CVE-2026-30956/): OneUptime has authorization bypass via client‑controlled is-multi-tenant-query header (critical 10.0)
- [CVE-2026-30957](https://insights.sbomify.com/CVE-2026-30957/): OneUptime Synthetic Monitor RCE via exposed Playwright browser object (critical 10.0)
- [CVE-2026-30887](https://insights.sbomify.com/CVE-2026-30887/): OneUptime Affected by Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33143 and fix it if it is affected.

What it is: CVE-2026-33143 is a high-severity missing authorization vulnerability in oneuptime, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33143 exists.

Affected packages and fixed versions:
- oneuptime (npm): affected all versions; fixed in 10.0.34
- oneuptime (npm): affected all versions; fixed in 10.0.34

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33143/ (Markdown: https://insights.sbomify.com/CVE-2026-33143/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33143
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33143
- OSV: https://osv.dev/vulnerability/CVE-2026-33143

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33143/
Summaries are generated and may contain mistakes; the official description above is the record.