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 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.
- BDU:2026-05074
- ALSA-2025:21462
- ALSA-2025:21628
- DLA-4397-1
- DSA-6058-1
- openSUSE-SU-2025:20083-1
- 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
- SUSE-SU-2025:21140-1
- Published
- Nov 5, 2025
- Updated
- Jun 17, 2026
- EPSS
- 1.1% · 63th percentile
- CWE
- CWE-843
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · talos
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| entrouvert | lasso | cpe:2.3:a:entrouvert:lasso |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- entrouvert lasso2.5.1
- entrouvert lasso2.8.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (talos). Independent of NVD's CPE analysis and usually ahead of it.
Entr'ouvert Lasso
- 2.5.1, 2.8.2affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | lasso | before 2.6.0-14.el8_10 | 2.6.0-14.el8_10 |
| AlmaLinux:8 | lasso-devel | before 2.6.0-14.el8_10 | 2.6.0-14.el8_10 |
| AlmaLinux:8 | python3-lasso | before 2.6.0-14.el8_10 | 2.6.0-14.el8_10 |
| AlmaLinux:9 | lasso | before 2.7.0-11.el9_7.3 | 2.7.0-11.el9_7.3 |
| AlmaLinux:9 | lasso-devel | before 2.7.0-11.el9_7.3 | 2.7.0-11.el9_7.3 |
| AlmaLinux:9 | python3-lasso | before 2.7.0-11.el9_7.3 | 2.7.0-11.el9_7.3 |
| Debian:11 | lasso | before 2.6.1-3+deb11u1 | 2.6.1-3+deb11u1 |
| Debian:12 | lasso | before 2.8.1-1+deb12u1 | 2.8.1-1+deb12u1 |
| Debian:13 | lasso | before 2.8.2-9+deb13u1 | 2.8.2-9+deb13u1 |
| Debian:14 | lasso | before 2.9.0-1 | 2.9.0-1 |
| openSUSE:Leap 16.0 | lasso | before 2.8.2-160000.3.1 | 2.8.2-160000.3.1 |
| Red Hat:enterprise_linux:8::appstream | java-lasso-debuginfo | before 0:2.6.0-14.el8_10 | 0:2.6.0-14.el8_10 |
| Red Hat:enterprise_linux:8::appstream | lasso | before 0:2.6.0-14.el8_10 | 0:2.6.0-14.el8_10 |
| Red Hat:enterprise_linux:8::appstream | lasso-debuginfo | before 0:2.6.0-14.el8_10 | 0:2.6.0-14.el8_10 |
| Red Hat:enterprise_linux:8::appstream | lasso-debugsource | before 0:2.6.0-14.el8_10 | 0:2.6.0-14.el8_10 |
| Red Hat:enterprise_linux:8::appstream | perl-lasso-debuginfo | before 0:2.6.0-14.el8_10 | 0:2.6.0-14.el8_10 |
| Red Hat:enterprise_linux:8::appstream | python3-lasso | before 0:2.6.0-14.el8_10 | 0:2.6.0-14.el8_10 |
| Red Hat:enterprise_linux:8::appstream | python3-lasso-debuginfo | before 0:2.6.0-14.el8_10 | 0:2.6.0-14.el8_10 |
| Red Hat:enterprise_linux:8::crb | lasso-devel | before 0:2.6.0-14.el8_10 | 0:2.6.0-14.el8_10 |
| Red Hat:enterprise_linux:9::appstream | lasso | before 0:2.7.0-11.el9_7.3 | 0:2.7.0-11.el9_7.3 |
| Red Hat:enterprise_linux:9::appstream | lasso-debuginfo | before 0:2.7.0-11.el9_7.3 | 0:2.7.0-11.el9_7.3 |
| Red Hat:enterprise_linux:9::appstream | lasso-debugsource | before 0:2.7.0-11.el9_7.3 | 0:2.7.0-11.el9_7.3 |
| Red Hat:enterprise_linux:9::appstream | perl-lasso-debuginfo | before 0:2.7.0-11.el9_7.3 | 0:2.7.0-11.el9_7.3 |
| Red Hat:enterprise_linux:9::appstream | python3-lasso | before 0:2.7.0-11.el9_7.3 | 0:2.7.0-11.el9_7.3 |
+63
Same product
entrouvert: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-46784A denial of service vulnerability exists in the lasso_node_init_from_message_with_format functionality of Entr'ouvert Lasso 2.5.1.30Monitor
- CVE-2025-46705A denial of service vulnerability exists in the g_assert_not_reached functionality of Entr'ouvert Lasso 2.5.1 and 2.8.2.30Monitor
- CVE-2025-46404A denial of service vulnerability exists in the lasso_provider_verify_saml_signature functionality of Entr'ouvert Lasso 2.5.1.30Monitor
- CVE-2021-28091Lasso all versions prior to 2.7.0 has improper verification of a cryptographic signature.30Monitor
- CVE-2009-0050Lasso 2.2.1 and earlier does not properly check the return value from the OpenSSL DSA_verify function, which allows remote attackers to bypa17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:lasso | 2.7.0-11.el9_7.3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:lasso-devel | 2.7.0-11.el9_7.3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:python3-lasso | 2.7.0-11.el9_7.3 · AlmaLinux:9 | Package registry (OSV) |
| debian:lasso | 2.8.1-1+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:lasso | 2.8.2-150600.3.5.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| red hat:java-lasso-debuginfo | 0:2.6.0-8.el8_2.1 · Red Hat:rhel_aus:8.2::appstream | Package registry (OSV) |
| red hat:lasso | 0:2.6.0-8.el8_2.1 · Red Hat:rhel_aus:8.2::appstream | Package registry (OSV) |
| red hat:lasso-debuginfo | 0:2.6.0-8.el8_2.1 · Red Hat:rhel_aus:8.2::appstream | Package registry (OSV) |
| red hat:lasso-debugsource | 0:2.6.0-8.el8_2.1 · Red Hat:rhel_aus:8.2::appstream | Package registry (OSV) |
| red hat:lasso-devel | 0:2.7.0-11.el9_4.1 · Red Hat:rhel_eus:9.4::crb | Package registry (OSV) |
| red hat:lasso-python | 0:2.5.1-8.el7_9.1 · Red Hat:rhel_els:7 | Package registry (OSV) |
| red hat:perl-lasso-debuginfo | 0:2.6.0-8.el8_2.1 · Red Hat:rhel_aus:8.2::appstream | Package registry (OSV) |
| red hat:python3-lasso | 0:2.6.0-13.el8_8.1 · Red Hat:rhel_e4s:8.8::appstream | Package registry (OSV) |
| red hat:python3-lasso-debuginfo | 0:2.6.0-8.el8_2.1 · Red Hat:rhel_aus:8.2::appstream | Package registry (OSV) |
| rocky linux:lasso | 0:2.7.0-11.el9_7.3 · Rocky Linux:9 | Package registry (OSV) |
| suse:lasso | 2.8.2-150600.3.5.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP6 | Package registry (OSV) |
| suse:lasso | 2.8.2-160000.3.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Keane O'Kelleyand another member of Cisco Advanced Security Initiative Group
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-843 · Access of Resource Using Incompatible Type ('Type Confusion')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →