LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1484: Glib: integer overflow leading to buffer underflow and out-of-bounds write in glib g_base64_encode()

A flaw was found in the GLib Base64 encoding routine when processing very large input data. Due to incorrect use of integer types during length calculation, the library may miscalculate buffer boundaries. This can cause memory writes outside the allocated buffer. Applications that process untrusted or extremely large Base64 input using GLib may crash or behave unpredictably.

MediumCVSS 4.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a GLib memory-safety flaw in Base64 encoding. Very large data can make GLib miscalculate buffer boundaries, causing writes outside the allocated memory. Business impact is mainly crash or unpredictable application behavior, with limited integrity and availability impact in the supplied CVSS data.

Executive priority

Treat this as a moderate patch-management and exposure-review item, not an emergency based on supplied evidence. Focus first on systems that process external large files or data streams, then track vendor fixes and apply them through normal maintenance windows.

Technical view

CVE-2026-1484 affects GLib g_base64_encode(). Incorrect integer type use during length calculation can cause integer overflow, buffer underflow, and out-of-bounds write. Red Hat rates it medium, CVSS 4.2, with network vector, high complexity, no privileges, user interaction required, and low integrity and availability impact.

Likely exposure

Exposure is most likely where affected Red Hat Enterprise Linux 6, 7, 8, 9, or 10 systems run glib2 or listed dependent packages and applications process untrusted or extremely large data through GLib Base64 encoding.

Exploitation context

The supplied sources do not state active exploitation, and KEV status is false. The CVSS vector indicates exploitation is not straightforward: attack complexity is high and user interaction is required. Evidence for practical exploitability is incomplete in the provided bundle.

Researcher notes

The core issue is CWE-787 out-of-bounds write after integer overflow in GLib Base64 output length handling. The bundle names affected Red Hat packages but does not provide fixed versions, proof-of-concept details, or confirmed exploitation. Avoid assuming all GLib consumers are reachable.

Mitigation direction

  • Check Red Hat, GNOME GLib, and Siemens advisories for fixed versions or vendor workarounds.
  • Update affected glib2 and related packages when vendor fixes are available.
  • Limit untrusted or extremely large data reaching GLib Base64 encoding paths.
  • Apply input-size controls in applications that encode externally supplied data.
  • Prioritize internet-facing or automation-heavy systems that process large external files.

Validation and detection

  • Inventory RHEL systems and packages listed as affected in the source bundle.
  • Identify applications using GLib g_base64_encode() on untrusted or very large input.
  • Confirm whether vendor fixed builds or advisories exist for each installed package stream.
  • Review crash reports for GLib-related memory faults during Base64 encoding.
  • Test input-size limits and error handling in affected application paths.
Prepared
Confidence
medium
Sources
6

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-787: 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-1484 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
4.2 (3.1)
Known Exploited
No
Published

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

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
5Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical 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
4.2CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L1.62.5redhat

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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. Source timelineredhat

    Made public.

  2. Source timelineredhat

    Reported to Red Hat.

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

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

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Red HatRed Hat Enterprise Linux 10bootcaffected
Red HatRed Hat Enterprise Linux 10glib2affected
Red HatRed Hat Enterprise Linux 10glycin-loadersaffected
Red HatRed Hat Enterprise Linux 10loupeaffected
Red HatRed Hat Enterprise Linux 10mingw-glib2affected
Red HatRed Hat Enterprise Linux 10papersaffected
Red HatRed Hat Enterprise Linux 10rpm-ostreeaffected
Red HatRed Hat Enterprise Linux 6glib2affected
Red HatRed Hat Enterprise Linux 7glib2affected
Red HatRed Hat Enterprise Linux 8glib2affected
Red HatRed Hat Enterprise Linux 8librsvg2affected
Red HatRed Hat Enterprise Linux 8mingw-glib2affected
Red HatRed Hat Enterprise Linux 9bootcaffected
Red HatRed Hat Enterprise Linux 9glib2affected
Red HatRed Hat Enterprise Linux 9librsvg2affected
Red HatRed Hat Enterprise Linux 9mingw-glib2affected
Weakness

CWE details

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

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.