LiveActive security incident?Get immediate response
CVE Record

CVE-2026-48840: Exim 4.88 before 4.99.4, in some proxy configurations, mishandles certain short payloads, leading to disclo...

Exim 4.88 before 4.99.4, in some proxy configurations, mishandles certain short payloads, leading to disclosure of uninitialized stack memory values to a client.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE is a remote information disclosure issue in Exim. In some proxy configurations, specially short client payloads can cause Exim to return uninitialized stack memory. The known impact is limited confidentiality exposure, not takeover or service outage.

Executive priority

Treat this as a moderate-priority mail infrastructure update. It is remotely reachable and unauthenticated, but current sources indicate limited data exposure and no confirmed active exploitation.

Technical view

Exim 4.88 before 4.99.4 mishandles certain short payloads in some proxy configurations, disclosing uninitialized stack memory to a client. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges, no user interaction, low confidentiality impact only.

Likely exposure

Exposure is most likely on internet-facing Exim mail servers running versions before 4.99.4 with the affected proxy configuration. Standard deployments without the relevant proxy setup may not be exposed, based on the limited source description.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. The CVSS vector indicates unauthenticated network reachability, but the described outcome is memory disclosure rather than code execution, integrity compromise, or denial of service.

Researcher notes

Key missing details are the exact proxy configuration requirements and practical leak contents. Avoid broad exposure claims unless configuration evidence exists. Validate version and deployment mode before escalating beyond medium severity.

Mitigation direction

  • Upgrade Exim to 4.99.4 or a distribution package containing that fix.
  • Apply Debian LTS or other vendor security updates where applicable.
  • Prioritize externally reachable Exim systems using proxy configurations.
  • If upgrade is delayed, follow Exim vendor guidance rather than assuming a workaround.

Validation and detection

  • Inventory Exim versions and flag any before 4.99.4.
  • Identify Exim deployments using proxy configurations.
  • Confirm patched package versions against vendor or distribution advisories.
  • Verify no internet-facing vulnerable Exim instances remain after maintenance.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-839: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-48840 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4mitre

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-48840Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
EximExim4.88unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-839 · source CWE mapping

Numeric Range Comparison Without Minimum Check

Numeric Range Comparison Without Minimum Check represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.