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

High 8.7 Published Updated

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

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

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

Which versions are affected by CVE-2026-33143?

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

PackageAffectedFixed in
oneuptime npmAll versions10.0.34
oneuptime npmAll versions10.0.34

Products include Hackerbay Oneuptime.

How do I fix CVE-2026-33143?

Upgrade oneuptime to 10.0.34 or later.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-33143 being exploited?

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

Sources

Also known as GHSA-g5ph-f57v-mwjc.

Is CVE-2026-33143 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free