# CVE-2025-7493: Freeipa: idm: privilege escalation from host to domain admin in freeipa > Attackers can escalate privileges from host to domain admin by exploiting missing validation of the root@REALM canonical name in FreeIPA. - **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 30 Sep 2025 - **Updated:** 26 Feb 2026 - **Also known as:** ALSA-2025:17084, ALSA-2025:17129, ALSA-2025:20928, ALSA-2025:20994, AZL-68190, CLSA-2025-1763391572, DEBIAN-CVE-2025-7493, GHSA-vm59-52f9-r52r, RHSA-2025:17084, RHSA-2025:17085, RHSA-2025:17086, RHSA-2025:17087, RHSA-2025:17088, RHSA-2025:17129, RHSA-2025:17645, RHSA-2025:17646, RHSA-2025:17647, RHSA-2025:17648, RHSA-2025:17649, RHSA-2025:20928, RHSA-2025:20994, RLSA-2025:17084, RLSA-2025:17085, RLSA-2025:17129, RLSA-2025:20928, RLSA-2025:20994, UBUNTU-CVE-2025-7493 ## What is CVE-2025-7493? CVE-2025-7493 is a critical vulnerability in Red Hat Enterprise Linux 10, published on 30 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description A privilege escalation flaw from host to domain administrator was found in FreeIPA. This vulnerability is similar to CVE-2025-4404, where it fails to validate the uniqueness of the krbCanonicalName. While the previously released version added validations for the admin@REALM credential, FreeIPA still does not validate the root@REALM canonical name, which can also be used as the realm administrator's name. This flaw allows an attacker to perform administrative tasks over the REALM, leading to access to sensitive data and sensitive data exfiltration. Weakness: CWE-1220 (Insufficient Granularity of Access Control) ## Which versions are affected by CVE-2025-7493? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ipa-client-common` | AlmaLinux:10 | All versions | 4.12.2-24.el10_1.1 | | `ipa-common` | AlmaLinux:10 | All versions | 4.12.2-24.el10_1.1 | | `ipa-selinux` | AlmaLinux:10 | All versions | 4.12.2-24.el10_1.1 | | `ipa-selinux-luna` | AlmaLinux:10 | All versions | 4.12.2-24.el10_1.1 | | `ipa-selinux-nfast` | AlmaLinux:10 | All versions | 4.12.2-24.el10_1.1 | | `ipa-server-common` | AlmaLinux:10 | All versions | 4.12.2-24.el10_1.1 | | `ipa-server-dns` | AlmaLinux:10 | All versions | 4.12.2-24.el10_1.1 | | `python3-ipaclient` | AlmaLinux:10 | All versions | 4.12.2-24.el10_1.1 | | `python3-ipalib` | AlmaLinux:10 | All versions | 4.12.2-24.el10_1.1 | | `python3-ipaserver` | AlmaLinux:10 | All versions | 4.12.2-24.el10_1.1 | | `python3-ipatests` | AlmaLinux:10 | All versions | 4.12.2-24.el10_1.1 | | `bind-dyndb-ldap` | AlmaLinux:8 | All versions | 11.6-6.module_el8.10.0+3980+d78e8e90 | | `custodia` | AlmaLinux:8 | All versions | 0.6.0-3.module_el8.6.0+2881+2f24dc92 | | `ipa-client` | AlmaLinux:8 | All versions | 4.9.13-20.module_el8.10.0+4050+3b475c71 | | `ipa-client-common` | AlmaLinux:8 | All versions | 4.9.13-20.module_el8.10.0+4050+3b475c71 | | `ipa-client-epn` | AlmaLinux:8 | All versions | 4.9.13-20.module_el8.10.0+4050+3b475c71 | | `ipa-client-samba` | AlmaLinux:8 | All versions | 4.9.13-20.module_el8.10.0+4050+3b475c71 | | `ipa-common` | AlmaLinux:8 | All versions | 4.9.13-20.module_el8.10.0+4050+3b475c71 | | `ipa-healthcheck` | AlmaLinux:8 | All versions | 0.12-6.module_el8.10.0+4036+84b152d9 | | `ipa-healthcheck-core` | AlmaLinux:8 | All versions | 0.12-6.module_el8.10.0+4036+84b152d9 | | `ipa-python-compat` | AlmaLinux:8 | All versions | 4.9.13-20.module_el8.10.0+4050+3b475c71 | | `ipa-selinux` | AlmaLinux:8 | All versions | 4.9.13-20.module_el8.10.0+4050+3b475c71 | | `ipa-server` | AlmaLinux:8 | All versions | 4.9.13-20.module_el8.10.0+4050+3b475c71 | | `ipa-server-common` | AlmaLinux:8 | All versions | 4.9.13-20.module_el8.10.0+4050+3b475c71 | | `ipa-server-dns` | AlmaLinux:8 | All versions | 4.9.13-20.module_el8.10.0+4050+3b475c71 | | `ipa-server-trust-ad` | AlmaLinux:8 | All versions | 4.9.13-20.module_el8.10.0+4050+3b475c71 | | `opendnssec` | AlmaLinux:8 | All versions | 2.1.7-2.module_el8.10.0+3980+d78e8e90 | | `python3-custodia` | AlmaLinux:8 | All versions | 0.6.0-3.module_el8.6.0+2881+2f24dc92 | | `python3-ipaclient` | AlmaLinux:8 | All versions | 4.9.13-20.module_el8.10.0+4050+3b475c71 | | `python3-ipalib` | AlmaLinux:8 | All versions | 4.9.13-20.module_el8.10.0+4050+3b475c71 | | `python3-ipaserver` | AlmaLinux:8 | All versions | 4.9.13-20.module_el8.10.0+4050+3b475c71 | | `python3-ipatests` | AlmaLinux:8 | All versions | 4.9.13-20.module_el8.10.0+4050+3b475c71 | | `python3-jwcrypto` | AlmaLinux:8 | All versions | 0.5.0-2.module_el8.10.0+3844+20e075e5 | | `python3-kdcproxy` | AlmaLinux:8 | All versions | 0.4-5.module_el8.10.0+3942+63b39a46.1 | | `python3-pyusb` | AlmaLinux:8 | All versions | 1.0.0-9.1.module_el8.7.0+3349+cfeff52e | | `python3-qrcode` | AlmaLinux:8 | All versions | 5.3-1.module_el8.10.0+3942+63b39a46 | | `python3-qrcode-core` | AlmaLinux:8 | All versions | 5.3-1.module_el8.10.0+3942+63b39a46 | | `python3-yubico` | AlmaLinux:8 | All versions | 1.3.2-9.1.module_el8.7.0+3349+cfeff52e | | `slapi-nis` | AlmaLinux:8 | All versions | 0.60.0-4.module_el8.10.0+3844+20e075e5.alma.1 | | `softhsm` | AlmaLinux:8 | All versions | 2.6.0-5.module_el8.6.0+2881+2f24dc92 | ## How do I fix CVE-2025-7493? Apply the vendor's patch. ## Is CVE-2025-7493 being exploited? There is no known exploitation of CVE-2025-7493 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-7493 and fix it if it is affected. What it is: CVE-2025-7493 is a critical vulnerability in Red Hat Enterprise Linux 10, published on 30 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-7493 in the wild and no public exploit code. Affected product: Red Hat Enterprise Linux 10. 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-7493/ (Markdown: https://insights.sbomify.com/CVE-2025-7493/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-7493 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-7493 - OSV: https://osv.dev/vulnerability/CVE-2025-7493 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-7493/ Summaries are generated and may contain mistakes; the official description above is the record.