# CVE-2025-7738: Python3.11-django-ansible-base: sensitive authenticator secrets returned in clear text via api in aap

> Privileged users can view GitHub Enterprise client secrets in clear text via the Gateway API, risking credential exposure.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jul 2025
- **Updated:** 23 Dec 2025
- **Also known as:** GHSA-qgmq-rhmw-xw3r

## What is CVE-2025-7738?

CVE-2025-7738 is a medium-severity vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8, published on 31 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in Ansible Automation Platform (AAP) where the Gateway API returns the client secret for certain GitHub Enterprise authenticators in clear text. This vulnerability affects administrators or auditors accessing authenticator configurations. While access is limited to privileged users, the clear text exposure of sensitive credentials increases the risk of accidental leaks or misuse.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2025-7738?


## How do I fix CVE-2025-7738?

Apply the vendor's patch.

## Is CVE-2025-7738 being exploited?

There is no known exploitation of CVE-2025-7738 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7738 and fix it if it is affected.

What it is: CVE-2025-7738 is a medium-severity vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8, published on 31 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-7738 in the wild and no public exploit code.

Affected product: Red Hat Ansible Automation Platform 2.5 for RHEL 8. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-7738/ (Markdown: https://insights.sbomify.com/CVE-2025-7738/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-7738
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-7738
- OSV: https://osv.dev/vulnerability/CVE-2025-7738

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-7738/
Summaries are generated and may contain mistakes; the official description above is the record.