CVE-2026-128334 in Listmonkinfo

Summary

by MITRE • 11/13/2026

listmonk 6.2.0 before 7.0.0-beta.2 contains a missing authentication vulnerability that allows unauthenticated attackers to submit Azure Event Grid bounce webhooks when no shared secret is configured. Attackers can POST forged EmailDeliveryReportReceived events with Bounced status to /webhooks/service/azure to blocklist, unsubscribe, or delete arbitrary subscribers.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/13/2026

The identified vulnerability in listmonk versions prior to 7.0.0-beta.2 represents a critical authentication bypass within the Azure Event Grid webhook integration mechanism. This flaw stems from an incomplete implementation of access control checks for specific API endpoints designed to receive external event notifications. Specifically, the endpoint located at /webhooks/service/azure fails to enforce mandatory authentication when the system administrator has not configured a shared secret key. In secure architectures, such webhooks typically require either mutual TLS authentication or a signed request with a pre-shared cryptographic key to verify the identity of the sender and ensure data integrity. The absence of this validation step allows any actor on the internet to interact directly with the webhook endpoint without providing valid credentials, effectively treating an administrative interface as public-facing.

The technical exploitation of this vulnerability involves crafting and sending HTTP POST requests containing forged Azure Event Grid bounce notifications. An attacker can construct a malicious payload mimicking the structure of a legitimate EmailDeliveryReportReceived event, specifically setting the status field to Bounced. By submitting these fabricated events through the unauthenticated endpoint, the attacker tricks listmonk into processing them as genuine delivery failure reports from Microsoft's email infrastructure. This manipulation exploits the trust relationship between the application and its cloud provider services, allowing the injection of false negative feedback regarding specific subscriber interactions. The vulnerability is particularly dangerous because it leverages legitimate system functionality for malicious purposes, making detection through standard logging mechanisms more challenging without deep packet inspection or behavioral analysis.

The operational impact of this flaw is severe, primarily affecting data integrity and availability within email marketing campaigns. By successfully submitting forged bounce events, an attacker can systematically blocklist innocent subscribers who have not actually bounced their emails. This leads to the unintended removal of valid users from mailing lists, causing significant loss of audience reach and potential revenue for organizations relying on listmonk for communication. Furthermore, attackers may exploit this mechanism to unsubscribe arbitrary subscribers against their will, violating consent requirements under regulations such as GDPR or CAN-SPAM. In more aggressive scenarios, if the system allows deletion based on excessive bounces, an attacker could trigger mass deletions of subscriber records, resulting in permanent data loss and requiring complex recovery procedures from backups.

To mitigate this vulnerability, administrators must immediately upgrade to listmonk version 7.0.0-beta.2 or later where these authentication checks have been reinforced. For environments that cannot yet upgrade, a temporary mitigation involves configuring the shared secret key within the application settings if not already present. This ensures that all incoming webhook requests are validated against the expected cryptographic signature before processing. Additionally, network-level controls such as IP allow-listing can be implemented to restrict access to the /webhooks/service/azure endpoint exclusively to known Azure Event Grid IP ranges. Regular security audits and penetration testing should also be conducted to verify that no other endpoints suffer from similar authentication omissions, ensuring comprehensive protection against unauthenticated API abuse.

This vulnerability aligns with CWE-287, which describes Improper Authentication, as the system failed to adequately prove the identity of a user attempting to access resources. It also maps to MITRE ATT&CK technique T1496, Resource Hijacking via Cloud Infrastructure, where attackers manipulate cloud services to cause denial of service or data corruption. The exploitation vector falls under T1078, Valid Accounts, although in this case it is more accurately described as exploiting a lack of required authentication for a privileged function. Understanding these classifications helps security teams contextualize the risk within broader threat landscapes and prioritize remediation efforts based on industry-standard frameworks.

Responsible

VulnCheck

Reservation

11/13/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00366

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!