Skip to content
Noroxi
NVD / CVE Program· CNA talos

CVE-2025-47151: 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.

Noroxi assessment

Priority: Monitor (action score 39/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 65.2% of all records.
  • 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.
  • Fixed version: lasso (AlmaLinux:8) 2.6.0-14.el8_10; lasso-devel (AlmaLinux:8) 2.6.0-14.el8_10; python3-lasso (AlmaLinux:8) 2.6.0-14.el8_10.

Low priority for now. Upgrade to lasso (AlmaLinux:8) 2.6.0-14.el8_10; lasso-devel (AlmaLinux:8) 2.6.0-14.el8_10; python3-lasso (AlmaLinux:8) 2.6.0-14.el8_10 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Nov 5, 2025
Updated
Oct 18, 2026
EPSS
1.0% · 65th percentile

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.0%

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.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-47151

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for entrouvert records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
entrouvertlasso

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.

EcosystemPackageAffected rangeFix
AlmaLinux:8lassobefore 2.6.0-14.el8_102.6.0-14.el8_10
AlmaLinux:8lasso-develbefore 2.6.0-14.el8_102.6.0-14.el8_10
AlmaLinux:8python3-lassobefore 2.6.0-14.el8_102.6.0-14.el8_10
AlmaLinux:9lassobefore 2.7.0-11.el9_7.32.7.0-11.el9_7.3
AlmaLinux:9lasso-develbefore 2.7.0-11.el9_7.32.7.0-11.el9_7.3
AlmaLinux:9python3-lassobefore 2.7.0-11.el9_7.32.7.0-11.el9_7.3
Debian:11lassobefore 2.6.1-3+deb11u12.6.1-3+deb11u1
Debian:12lassobefore 2.8.1-1+deb12u12.8.1-1+deb12u1
Debian:13lassobefore 2.8.2-9+deb13u12.8.2-9+deb13u1
Debian:14lassobefore 2.9.0-12.9.0-1
openSUSE:Leap 15.6lassobefore 2.8.2-150600.3.5.12.8.2-150600.3.5.1
openSUSE:Leap 16.0lassobefore 2.8.2-160000.3.12.8.2-160000.3.1
Red Hat:enterprise_linux:8::appstreamjava-lasso-debuginfobefore 0:2.6.0-14.el8_100:2.6.0-14.el8_10
Red Hat:enterprise_linux:8::appstreamlassobefore 0:2.6.0-14.el8_100:2.6.0-14.el8_10
Red Hat:enterprise_linux:8::appstreamlasso-debuginfobefore 0:2.6.0-14.el8_100:2.6.0-14.el8_10
Red Hat:enterprise_linux:8::appstreamlasso-debugsourcebefore 0:2.6.0-14.el8_100:2.6.0-14.el8_10
Red Hat:enterprise_linux:8::appstreamperl-lasso-debuginfobefore 0:2.6.0-14.el8_100:2.6.0-14.el8_10
Red Hat:enterprise_linux:8::appstreampython3-lassobefore 0:2.6.0-14.el8_100:2.6.0-14.el8_10
Red Hat:enterprise_linux:8::appstreampython3-lasso-debuginfobefore 0:2.6.0-14.el8_100:2.6.0-14.el8_10
Red Hat:enterprise_linux:8::crblasso-develbefore 0:2.6.0-14.el8_100:2.6.0-14.el8_10
Red Hat:enterprise_linux:9::appstreamlassobefore 0:2.7.0-11.el9_7.30:2.7.0-11.el9_7.3
Red Hat:enterprise_linux:9::appstreamlasso-debuginfobefore 0:2.7.0-11.el9_7.30:2.7.0-11.el9_7.3
Red Hat:enterprise_linux:9::appstreamlasso-debugsourcebefore 0:2.7.0-11.el9_7.30:2.7.0-11.el9_7.3
Red Hat:enterprise_linux:9::appstreamperl-lasso-debuginfobefore 0:2.7.0-11.el9_7.30:2.7.0-11.el9_7.3

+63

Same product

entrouvert: all records

Other 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

Published before and after this one in the same product

  • ← EarlierCVE-2009-0050Jan 7, 2009 · Lasso 2.2.1 and earlier does not properly check the return value from the OpenSSL DSA_verify function, which allows remote attackers to bypa
    17Monitor
  • ← EarlierCVE-2021-28091Jun 4, 2021 · Lasso all versions prior to 2.7.0 has improper verification of a cryptographic signature.
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:lasso2.7.0-11.el9_7.3 · AlmaLinux:9Package registry (OSV)
almalinux:lasso-devel2.7.0-11.el9_7.3 · AlmaLinux:9Package registry (OSV)
almalinux:python3-lasso2.7.0-11.el9_7.3 · AlmaLinux:9Package registry (OSV)
debian:lasso2.8.1-1+deb12u1 · Debian:12Package registry (OSV)
opensuse:lasso2.8.2-150600.3.5.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:java-lasso-debuginfo0:2.6.0-8.el8_2.1 · Red Hat:rhel_aus:8.2::appstreamPackage registry (OSV)
red hat:lasso0:2.6.0-8.el8_2.1 · Red Hat:rhel_aus:8.2::appstreamPackage registry (OSV)
red hat:lasso-debuginfo0:2.6.0-8.el8_2.1 · Red Hat:rhel_aus:8.2::appstreamPackage registry (OSV)
red hat:lasso-debugsource0:2.6.0-8.el8_2.1 · Red Hat:rhel_aus:8.2::appstreamPackage registry (OSV)
red hat:lasso-devel0:2.7.0-11.el9_4.1 · Red Hat:rhel_eus:9.4::crbPackage registry (OSV)
red hat:lasso-python0:2.5.1-8.el7_9.1 · Red Hat:rhel_els:7Package registry (OSV)
red hat:perl-lasso-debuginfo0:2.6.0-8.el8_2.1 · Red Hat:rhel_aus:8.2::appstreamPackage registry (OSV)
red hat:python3-lasso0:2.6.0-13.el8_8.1 · Red Hat:rhel_e4s:8.8::appstreamPackage registry (OSV)
red hat:python3-lasso-debuginfo0:2.6.0-8.el8_2.1 · Red Hat:rhel_aus:8.2::appstreamPackage registry (OSV)
rocky linux:lasso0:2.7.0-11.el9_7.3 · Rocky Linux:9Package registry (OSV)
suse:lasso2.8.2-150600.3.5.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP6Package registry (OSV)
suse:lasso2.8.2-160000.3.1 · SUSE:Linux Enterprise Server 16.0Package 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.

EPSS, last 120 days

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 researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

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.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

All records