dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2026-11820

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The community.general Ansible collection's nexmo module sends Vonage/Nexmo API credentials (api_key and api_secret) as URL query parameters in GET requests. Although Ansible marks these parameters as no_log to prevent logging in Ansible's output, the credentials are still exposed in the actual HTTP requests and subsequently recorded in web server access logs, proxy logs, HTTP Referer headers, and network monitoring tools.

MitigationReplace GET requests with query parameter credentials with POST requests that send credentials in the request body, ensuring credentials never appear in URLs or associated logs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise LinuxOperating system
Affected:= 8.0= 9.0= 10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the nexmo module from community.general is in use
    Search playbooks, roles, and task files for 'nexmo' module references, or list installed Ansible collections with 'ansible-galaxy collection list' and look for community.general
    Affected if The nexmo module from community.general is being used in any playbook or role
  2. Check community.general collection version
    Run 'ansible-galaxy collection list' to see installed collection versions, or check the collection's metadata file at ~/.ansible/collections/ansible_collections/community/general/MANIFEST.json
    Affected if The installed community.general version falls within affected ranges for this vulnerability (consult CVE database for specific version ranges)
  3. Verify nexmo module credentials configuration
    Review playbooks or variable files that invoke the nexmo module and examine whether api_key and/or api_secret parameters are defined and passed to the module
    Affected if The nexmo module is configured with api_key and/or api_secret parameters that would be sent as URL query parameters
  4. Inspect HTTP traffic or logs for credential exposure
    Capture network traffic or review web server, proxy, and access logs where the nexmo module has made API calls to identify if credentials appear in URLs
    Affected if Credentials are observed in URL query strings (e.g., ?api_key=XXX&api_secret=XXX) in any captured traffic or logs

A defender is affected if they use the community.general collection's nexmo module with configured API credentials, as these credentials will be transmitted in GET request URLs and potentially logged.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace GET requests with query parameter credentials with POST requests that send credentials in the request body, ensuring credentials never appear in URLs or associated logs.

Fix this in Enterprise Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11820 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11820 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data