CVE-2026-84918: Monobank payment API - Moderately critical - Access bypass - SA-CONTRIB-2026-130

Q: Which deployments should be treated as affected?

Drupal sites using Monobank payment API versions from 0.0.0 through 1.0.3 are affected.

Q: What capability would an attacker need to exploit this issue?

The issue allows signature spoofing because cryptographic signatures are improperly verified. The available information does not specify any additional access or configuration requirements.

Q: How can I determine whether my site is affected?

Identify the installed Monobank payment API version. Versions up to and including 1.0.3 fall within the affected range.

Published Oct 22, 2026

Updated

Improper Verification of Cryptographic Signature vulnerability in Drupal Monobank payment API allows Signature Spoof. This issue affects Monobank payment API versions: from 0.0.0 to 1.0.3.

Affected Software

1 affected component

Drupal Monobank payment API>=0.0.0<=1.0.3

Event History

Oct 22, 2026

CVE Published

via MITRE·01:22 AM

Data Sourced

via MITRE·01:22 AM

DescriptionWeakness

Frequently Asked Questions

Which deployments should be treated as affected?

Drupal sites using Monobank payment API versions from 0.0.0 through 1.0.3 are affected.

What capability would an attacker need to exploit this issue?

The issue allows signature spoofing because cryptographic signatures are improperly verified. The available information does not specify any additional access or configuration requirements.

How can I determine whether my site is affected?

Identify the installed Monobank payment API version. Versions up to and including 1.0.3 fall within the affected range.

CVE-2026-84918: Monobank payment API - Moderately critical - Access bypass - SA-CONTRIB-2026-130

Affected Software

Event History

Frequently Asked Questions

Which deployments should be treated as affected?

What capability would an attacker need to exploit this issue?

How can I determine whether my site is affected?

Company

Resources

Contact

Frequently Asked Questions

Which deployments should be treated as affected?

What capability would an attacker need to exploit this issue?

How can I determine whether my site is affected?