BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-94184High confidence

Fetchmail: fetchmail: stack-based buffer overflow in ntlm authentication (fetchmail-sa-2026-01)

Red Hat · Red Hat Enterprise Linux 10

5.3MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.82% for the current model date.

Compensating controls

  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Red Hat Red Hat Enterprise Linux 10 and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcefetchmailAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 9 Oct 2026
Debian bookwormbookworm · sourcefetchmailAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 9 Oct 2026
Debian forkyforky · sourcefetchmailVendor fix publishedDebian records a fixed source-package version for this release.6.6.8-1Debian Security Tracker ↗Source updated 9 Oct 2026
Debian sidsid · sourcefetchmailVendor fix publishedDebian records a fixed source-package version for this release.6.6.8-1Debian Security Tracker ↗Source updated 9 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivefetchmailUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 8 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-94184 · CSAF 2.0 · revision 4 · interimSUSE Product Security TeamCVE-2026-94184
86 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • fetchmail as component of SUSE Linux Enterprise Desktop 15 SP7
  • fetchmailconf as component of SUSE Linux Enterprise Desktop 15 SP7
  • SUSE Linux Enterprise High Performance Computing 12 SP3:fetchmail
  • SUSE Linux Enterprise High Performance Computing 12 SP3:fetchmailconf
  • fetchmail as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP3
Summary
A stack-based buffer overflow flaw was found in fetchmail when built with NTLM support. A malicious or compromised mail server advertising NTLM authentication can send a crafted Type 2 challenge that causes fetchmail to write past a fixed stack buffer while building the NTLM authenticate response. This may lead to remote code execution depending on stack-frame layout, or to authentication failure or process termination under memory hardening.
Remediation
No remediation text is recorded.
CVE-2026-94184 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityfetchmail: fetchmail: stack-based buffer overflow in NTLM authentication (fetchmail-SA-2026-01)
6 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • fetchmail.src as a component of Red Hat Enterprise Linux 10
  • fetchmail.src as a component of Red Hat Enterprise Linux 6
  • fetchmail.src as a component of Red Hat Enterprise Linux 7
  • fetchmail as a component of Red Hat Enterprise Linux 8
  • fetchmail.src as a component of Red Hat Enterprise Linux 8
  • fetchmail.src as a component of Red Hat Enterprise Linux 9
Summary
A stack-based buffer overflow flaw was found in fetchmail when built with NTLM support. A malicious or compromised mail server advertising NTLM authentication can send a crafted Type 2 challenge that causes fetchmail to write past a fixed stack buffer while building the NTLM authenticate response. This may lead to remote code execution depending on stack-frame layout, or to authentication failure or process termination under memory hardening.
Remediation
Rebuild fetchmail without --enable-NTLM (omit NTLM at configure time). Confirm with `fetchmail -V` that the build does not list +NTLM.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-83923

No EUVD known-exploited evidence

A stack-based buffer overflow flaw was found in fetchmail when built with NTLM support. A malicious or compromised mail server advertising NTLM authentication can send a crafted Type 2 challenge that causes fetchmail to write past a fixed stack buffer while building the NTLM authenticate response. This may lead to remote code execution depending on stack-frame layout, or to authentication failure or process termination under memory hardening.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
5.3 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
01

What, why and how

A stack-based buffer overflow flaw was found in fetchmail when built with NTLM support. A malicious or compromised mail server advertising NTLM authentication can send a crafted Type 2 challenge that causes fetchmail to write past a fixed stack buffer while building the NTLM authenticate response. This may lead to remote code execution depending on stack-frame layout, or to authentication failure or process termination under memory hardening.

What

A stack-based buffer overflow flaw was found in fetchmail when built with NTLM support. A malicious or compromised mail server advertising NTLM authentication can send a crafted Type 2 challenge that causes fetchmail to write past a fixed stack buffer while building the NTLM authenticate response. This may lead to remote code execution depending on stack-frame layout, or to authentication failure or process termination under memory hardening.

Why

A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

What

A stack-based buffer overflow flaw was found in fetchmail when built with NTLM support. A malicious or compromised mail server advertising NTLM authentication can send a crafted Type 2 challenge that causes fetchmail to write past a fixed stack buffer while building the NTLM authenticate response. This may lead to remote code execution depending on stack-frame layout, or to authentication failure or process termination under memory hardening.

Why

A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Stack-based Buffer Overflow → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-121 ↗

CWE-121: Stack-based Buffer Overflow. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkUnauthenticatedRemote code executionCWE-121
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-83923Official EUVD mapping

A stack-based buffer overflow flaw was found in fetchmail when built with NTLM support. A malicious or compromised mail server advertising NTLM authentication can send a crafted Type 2 challenge that causes fetchmail to write past a fixed stack buffer while building the NTLM authenticate response. This may lead to remote code execution depending on stack-frame layout, or to authentication failure or process termination under memory hardening.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3495fetchmail: Schwachstelle ermöglicht Codeausführung

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in fetchmail ausnutzen, um beliebigen Programmcode auszuführen.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
  • fetchmail as component of SUSE Linux Enterprise Desktop 15 SP7
  • fetchmailconf as component of SUSE Linux Enterprise Desktop 15 SP7
  • SUSE Linux Enterprise High Performance Computing 12 SP3:fetchmail
  • SUSE Linux Enterprise High Performance Computing 12 SP3:fetchmailconf
  • fetchmail as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS:fetchmail
  • SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS:fetchmailconf
  • fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS:fetchmail
  • SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS:fetchmailconf
  • fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP5
  • fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP5
  • fetchmail as component of SUSE Linux Enterprise Module for Basesystem 15 SP7
  • fetchmail as component of SUSE Linux Enterprise Module for Desktop Applications 15 SP7
  • fetchmailconf as component of SUSE Linux Enterprise Module for Desktop Applications 15 SP7
  • SUSE Linux Enterprise Server 12 SP3-TERADATA:fetchmail
  • SUSE Linux Enterprise Server 12 SP3-TERADATA:fetchmailconf
  • fetchmail as component of SUSE Linux Enterprise Server 12 SP5-LTSS
  • and 56 more
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 21 Sept 2026 · Last source change 1 Oct 2026, 17:15 UTC · CWE-121 · Stack-based Buffer Overflow

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-22
European sourceENISA EUVD · EUVD-2026-83923
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    fetchmail as component of SUSE Linux Enterprise Desktop 15 SP7; fetchmailconf as component of SUSE Linux Enterprise Desktop 15 SP7; fetchmail as component of SUSE Linux Enterprise High Performance Computing 12 SP5; fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 12 SP5; fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP1; fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP1; fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP2; fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP2; fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP3; fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP3; fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP4; fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP4; fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP5; fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP5; fetchmail as component of SUSE Linux Enterprise Module for Basesystem 15 SP7; fetchmail as component of SUSE Linux Enterprise Module for Desktop Applications 15 SP7; fetchmailconf as component of SUSE Linux Enterprise Module for Desktop Applications 15 SP7; fetchmail as component of SUSE Linux Enterprise Server 12 SP5-LTSS; fetchmailconf as component of SUSE Linux Enterprise Server 12 SP5-LTSS; fetchmail as component of SUSE Linux Enterprise Server 12 SP5; fetchmailconf as component of SUSE Linux Enterprise Server 12 SP5; fetchmail as component of SUSE Linux Enterprise Server 15 SP1-LTSS; fetchmailconf as component of SUSE Linux Enterprise Server 15 SP1-LTSS; fetchmail as component of SUSE Linux Enterprise Server 15 SP1; fetchmailconf as component of SUSE Linux Enterprise Server 15 SP1; fetchmail as component of SUSE Linux Enterprise Server 15 SP2-LTSS; and 46 more
    After
    fetchmail as component of SUSE Linux Enterprise Desktop 15 SP7; fetchmailconf as component of SUSE Linux Enterprise Desktop 15 SP7; SUSE Linux Enterprise High Performance Computing 12 SP3:fetchmail; SUSE Linux Enterprise High Performance Computing 12 SP3:fetchmailconf; fetchmail as component of SUSE Linux Enterprise High Performance Computing 12 SP5; fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 12 SP5; fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP1; fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP1; fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP2; fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP2; fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP3; fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP3; SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS:fetchmail; SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS:fetchmailconf; fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP4; fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP4; SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS:fetchmail; SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS:fetchmailconf; fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; fetchmail as component of SUSE Linux Enterprise High Performance Computing 15 SP5; fetchmailconf as component of SUSE Linux Enterprise High Performance Computing 15 SP5; fetchmail as component of SUSE Linux Enterprise Module for Basesystem 15 SP7; fetchmail as component of SUSE Linux Enterprise Module for Desktop Applications 15 SP7; fetchmailconf as component of SUSE Linux Enterprise Module for Desktop Applications 15 SP7; SUSE Linux Enterprise Server 12 SP3-TERADATA:fetchmail; SUSE Linux Enterprise Server 12 SP3-TERADATA:fetchmailconf; fetchmail as component of SUSE Linux Enterprise Server 12 SP5-LTSS; and 56 more
    SUSE Product Security Team ↗
  2. SeveritySeverity changed from High to Medium.
    Before
    High
    After
    Medium
    CNA ↗
  3. CVSS scoreCVSS score changed from 8.1 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) to 5.3 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).
    Before
    8.1 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)
    After
    5.3 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)
    CNA ↗
  4. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-94184 to remediation: access.redhat.com/CVE-2026-94184.
    Before
    remediation: access.redhat.com/CVE-2026-94184
    After
    remediation: access.redhat.com/CVE-2026-94184
    Red Hat Product Security ↗
  5. CVSS scoreCVSS scoring authority changed from CISA ADP to CNA; the displayed base score remained 8.1.
    Before
    8.1 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)
    After
    8.1 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)
    CNA ↗
  6. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    CISA ADP ↗
  7. CVSS scoreCVSS score changed from not recorded to 8.1 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).
    Before
    not recorded
    After
    8.1 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)
    CISA ADP ↗
  8. SeveritySeverity changed from High to Unknown.
    Before
    High
    After
    Unknown
    CVE.org ↗
  9. CVSS scoreCVSS score changed from 8.1 (CVSS 3.1 · Other authority · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) to not recorded.
    Before
    8.1 (CVSS 3.1 · Other authority · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)
    After
    not recorded
    CVE.org ↗
  10. CVSS scoreCVSS scoring authority changed from CNA to Other authority; the displayed base score remained 8.1.
    Before
    8.1 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)
    After
    8.1 (CVSS 3.1 · Other authority · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)
    Other authority ↗
  11. ENISA EUVD mappingEUVD-2026-83923 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-83923"}
    ENISA EUVD ↗
  12. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2026-83923↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-94184 · cve.blacktree.nl