CVE-2026-11820: Community.general: community.general nexmo — api credentials exposed in get url query string[security] community.general nexmo — api credentials exposed in get url query string

Published Jun 15, 2026
·
Updated

A flaw was found in the community.general Ansible collection's nexmo module. The module constructs HTTP requests to the Vonage/Nexmo SMS API by encoding API credentials (apikey and apisecret) into URL query parameters and sending them via GET requests. This causes credentials to be exposed in web server access logs, proxy logs, HTTP Referer headers, and network monitoring tools, despite the Ansible argument specification marking these parameters as nolog. An attacker with access to any of these logging or monitoring points can obtain the full API credentials and gain unauthorized access to the victim's Vonage/Nexmo account.

Other sources

apikey and apisecret are declared nolog=True at the input level, but both credentials are immediately URL-encoded into a GET request as query parameters, bypassing all nolog protection

Red Hat

Affected Software

4 affected components
ansible/collection/community.general/nexmo
redhat Enterprise Linux=8.0
redhat Enterprise Linux=9.0
redhat Enterprise Linux=10.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Switch the nexmo module implementation from building a GET request URL that includes query parameters for api_key/api_secret (e.g., constructing url = f"{NEXMO_API}?{urlencode(msg)}") to using POST with Content-Type: application/x-www-form-urlencoded and sending credentials in the request body (e.g., fetch_url(..., NEXMO_API, data=data, method="POST", headers={"Content-Type": "application/x-www-form-urlencoded"}).

    community.general Ansible collection (plugins/modules/nexmo.py) nexmo module HTTP method for Vonage/Nexmo SMS API call (GET vs POST) = POST

Event History

Jun 15, 2026
Data Sourced
via Red Hat·06:44 PM
DescriptionSeverityAffected Software
Jun 23, 2026
CVE Published
via MITRE·07:53 PM
Data Sourced
via MITRE·07:53 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-11820?

The severity of CVE-2026-11820 is rated as medium with a score of 6.5.

2

What issue does CVE-2026-11820 describe?

CVE-2026-11820 describes a vulnerability where API credentials are exposed in the URL query string, bypassing no_log protection.

3

How do I fix CVE-2026-11820?

To fix CVE-2026-11820, avoid exposing API credentials in query parameters and ensure they are handled securely.

4

What software is affected by CVE-2026-11820?

The vulnerability CVE-2026-11820 affects the Ansible community.general module specifically in nexmo.py.

5

What are the potential risks of CVE-2026-11820?

The potential risks of CVE-2026-11820 include unauthorized access to sensitive API credentials leading to data exposure.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203