CVE-2026-11820Community.general: community.general nexmo — api credentials exposed in get url query string[security] community.general nexmo — api credentials exposed in get url query string
- 6.5MediumCVSS base score
- 0.39%Exploitation in 30 daysEPSS · top 66% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By redhat
- 14 days later
· 14 days later
Published
- 5 months later
· 5 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| redhatCNA (assigner) | 3.1 | Medium6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVDNVD · Analyzed | 3.1 | Medium6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
- EPSS (exploitation in 30 days)
- 0.39% · top 66% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.5.
Affected products
Red Hat · Red Hat Enterprise Linux 10
All versions: unknown
Red Hat · Red Hat Enterprise Linux 8
All versions: unknown
Red Hat · Red Hat Enterprise Linux 8
All versions: unknown
Red Hat · Red Hat Enterprise Linux 9
All versions: unknown
What to do
Workaround: 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.
References
References2
- https://access.redhat.com/security/cve/CVE-2026-11820 (opens in a new tab)vdb-entryx_refsource_REDHAT
- RHBZ#2488970 (opens in a new tab)issue-trackingx_refsource_REDHAT
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-38605 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-11820)Record last updated .