CVE-2026-11820
Description
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 (api_key and api_secret) 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 no_log. 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.
Statement
Code Flaw initial found in community.general 13.0.0, however, the same code logic is found in older versions going back at least to 8.3.
This flaw affects the community.general Ansible collection's nexmo module in all versions prior to its removal in 9.0.0. Red Hat ships ansible-collection-community-general in several product streams (EPEL, Fedora, OpenStack). The vulnerability exposes Vonage/Nexmo API credentials in HTTP request URLs, making them available in server logs and network monitoring. The nexmo module is deprecated upstream and the recommended remediation is to stop using it in favor of direct API calls via the uri module.
Mitigation
The following practices would help for avoiding exposure and mitigate this
flaw:
- If possible, stop using the community.general nexmo module entirely. It is
deprecated upstream and was removed in community.general 9.0.0. Consider
using the Vonage API directly via the community.general uri module with
POST method and credentials in the request body.
- Review web server, proxy, and load balancer access logs for any recorded
Vonage API URLs containing api_key and api_secret parameters. Rotate any
credentials found in logs.
- Restrict access to HTTP access logs on systems where the nexmo module has
been used.
- Configure proxy and web server logging to redact or exclude query string
parameters from URL logging where possible.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 6.5 | N/A | 6.5 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | None | N/A | None |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
cve.org: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Application Data
Logging sensitive user data, full path names, or system information often provides attackers with an additional, less-protected path to acquiring the information.
Acknowledgements
Red Hat would like to thank Bipin Saud (https://www.linkedin.com/in/bipinsaud/) for reporting this issue.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
