Medium [CVE-2026-16566] jenkins_credential module returns generated API token in plaintext output
This medium-severity Red Hat Linux advisory covers CVE-2026-16566.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A flaw was found in the community.general Ansible collection's jenkins_credential module.
When creating a Jenkins API token (credential_type: token), the module correctly protects the input password with no_log=True in the argument specification, but places the generated API token returned by the Jenkins API directly into the Ansible task result dictionary without output suppression.
The token is emitted in plaintext via exit_json(), causing it to appear in Ansible task output, AWX/Tower/AAP Controller job logs, callback plugin output, CI/CD pipeline logs, and fact caching backends. An attacker with access to any of these output channels can obtain the Jenkins API token and gain the same privileges as the user who created it.
Red Hat severity: Moderate — CVSS 6.1 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N). Red Hat lists Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9 as not affected.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 17 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 17 days ago·verify at source
Mitigation checklist
- - Add no_log: true at the task level when using the jenkins_credential module with credential_type: token: - name: Create Jenkins API token community.general.jenkins_credential: credential_type: token jenkins_url: "{{ jenkins_url }}" jenkins_user: "{{ jenkins_user }}" jenkins_password: "{{ jenkins_password }}" register: token_result no_log: true - Review AWX/Tower/AAP Controller job logs, CI/CD pipeline logs, and callback plugin output for any previously leaked Jenkins API tokens. Rotate any tokens found in logs. - If fact caching is enabled, check the cache backend for registered variables containing jenkins_credential results.
Official advisory · high-confidence parse· fetched 17 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.