# CVE-2025-47151: Memory corruption in Lasso > A type confusion in the Lasso library allows attackers to execute arbitrary code via a crafted SAML response. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 5 Nov 2025 - **Updated:** 5 Nov 2025 - **Also known as:** ALSA-2025:21462, ALSA-2025:21628, AZL-69850, AZL-69863, CLSA-2025-1764677738, CLSA-2025-1765478656, DEBIAN-CVE-2025-47151, GHSA-j9px-r24r-fm3p, RHSA-2025:21399, RHSA-2025:21400, RHSA-2025:21401, RHSA-2025:21402, RHSA-2025:21403, RHSA-2025:21404, RHSA-2025:21405, RHSA-2025:21406, RHSA-2025:21452, RHSA-2025:21462, RHSA-2025:21628, RLSA-2025:21462, RLSA-2025:21628, UBUNTU-CVE-2025-47151 ## What is CVE-2025-47151? CVE-2025-47151 is a critical memory corruption vulnerability in Entr'ouvert Lasso, published on 5 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A type confusion vulnerability exists in the lasso_node_impl_init_from_xml functionality of Entr'ouvert Lasso 2.5.1 and 2.8.2. A specially crafted SAML response can lead to an arbitrary code execution. An attacker can send a malformed SAML response to trigger this vulnerability. Weakness: CWE-843 (Access of Resource Using Incompatible Type) ## Which versions are affected by CVE-2025-47151? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `lasso` | AlmaLinux:8 | All versions | 2.6.0-14.el8_10 | | `lasso-devel` | AlmaLinux:8 | All versions | 2.6.0-14.el8_10 | | `python3-lasso` | AlmaLinux:8 | All versions | 2.6.0-14.el8_10 | | `lasso` | AlmaLinux:9 | All versions | 2.7.0-11.el9_7.3 | | `lasso-devel` | AlmaLinux:9 | All versions | 2.7.0-11.el9_7.3 | | `python3-lasso` | AlmaLinux:9 | All versions | 2.7.0-11.el9_7.3 | | `java-lasso-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.6.0-14.el8_10 | | `lasso` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.6.0-14.el8_10 | | `lasso-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.6.0-14.el8_10 | | `lasso-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.6.0-14.el8_10 | | `perl-lasso-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.6.0-14.el8_10 | | `python3-lasso` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.6.0-14.el8_10 | | `python3-lasso-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.6.0-14.el8_10 | | `java-lasso-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.6.0-14.el8_10 | | `lasso-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.6.0-14.el8_10 | | `lasso-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.6.0-14.el8_10 | | `lasso-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.6.0-14.el8_10 | | `perl-lasso-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.6.0-14.el8_10 | | `python3-lasso-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.6.0-14.el8_10 | | `lasso` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.7.0-11.el9_7.3 | | `lasso-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.7.0-11.el9_7.3 | | `lasso-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.7.0-11.el9_7.3 | | `perl-lasso-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.7.0-11.el9_7.3 | | `python3-lasso` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.7.0-11.el9_7.3 | | `python3-lasso-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.7.0-11.el9_7.3 | | `lasso-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.7.0-11.el9_7.3 | | `lasso-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.7.0-11.el9_7.3 | | `lasso-devel` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.7.0-11.el9_7.3 | | `perl-lasso-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.7.0-11.el9_7.3 | | `python3-lasso-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.7.0-11.el9_7.3 | | `java-lasso-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.6.0-8.el8_2.1 | | `lasso` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.6.0-8.el8_2.1 | | `lasso-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.6.0-8.el8_2.1 | | `lasso-debugsource` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.6.0-8.el8_2.1 | | `perl-lasso-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.6.0-8.el8_2.1 | | `python3-lasso-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.6.0-8.el8_2.1 | | `java-lasso-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.6.0-8.el8_4.1 | | `lasso` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.6.0-8.el8_4.1 | | `lasso-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.6.0-8.el8_4.1 | | `lasso-debugsource` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.6.0-8.el8_4.1 | Products: Entrouvert Lasso. ## How do I fix CVE-2025-47151? Apply the vendor's patch. ## Is CVE-2025-47151 being exploited? There is no known exploitation of CVE-2025-47151 in the wild and no public exploit code. ## Other vulnerabilities in Entr'ouvert Lasso - [CVE-2025-46404](https://insights.sbomify.com/CVE-2025-46404/): Null dereference in Lasso (high 7.5) - [CVE-2025-46705](https://insights.sbomify.com/CVE-2025-46705/): Denial of service in Lasso (high 7.5) - [CVE-2025-46784](https://insights.sbomify.com/CVE-2025-46784/): Denial of service in Lasso (high 7.5) - [CVE-2015-1783](https://insights.sbomify.com/CVE-2015-1783/): Denial of service in n/a (high 7.5) - [CVE-2009-0050](https://insights.sbomify.com/CVE-2009-0050/): Security feature bypass in n/a (medium 4.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-47151 and fix it if it is affected. What it is: CVE-2025-47151 is a critical memory corruption vulnerability in Entr'ouvert Lasso, published on 5 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-47151 in the wild and no public exploit code. Affected product: Entr'ouvert Lasso. 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-47151/ (Markdown: https://insights.sbomify.com/CVE-2025-47151/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-47151 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-47151 - OSV: https://osv.dev/vulnerability/CVE-2025-47151 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-47151/ Summaries are generated and may contain mistakes; the official description above is the record.