LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1260: Invalid Memory Access in Sentencepiece,

Invalid memory access in Sentencepiece versions less than 0.2.1 when using a vulnerable model file, which is not created in the normal training procedure.

HighCVSS 8.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Sentencepiece can mishandle a specially formed model file and access memory incorrectly. Business risk is highest where ML or NLP systems load model files from outside trusted build pipelines. The source says the triggering model is not produced by normal training, which narrows typical exposure but does not eliminate risk from third-party artifacts.

Executive priority

Prioritize remediation for ML environments that ingest third-party or user-provided model files. Treat as high severity, but not an internet-wide emergency based on the provided evidence because exploitation requires loading a special model file and KEV is false.

Technical view

CVE-2026-1260 is a CWE-119 invalid memory access issue in Google Sentencepiece before 0.2.1. The CVSS 4.0 score is 8.5 High with local attack vector and user interaction required. Impact is rated high for vulnerable-system confidentiality, integrity, and availability when a vulnerable model file is loaded.

Likely exposure

Systems using Google Sentencepiece versions before 0.2.1 are potentially exposed if they load a vulnerable model file. Exposure is more likely in ML pipelines, research tooling, desktop workflows, or services that accept model files from third parties or users.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. Exploitation requires use of a vulnerable model file, and the CVE text says that file is not created by the normal training procedure. Evidence is insufficient to claim remote exploitation.

Researcher notes

Focus analysis on model-file trust boundaries and library version provenance. The source bundle does not provide exploit details, affected downstream applications, or proof of active exploitation. Avoid broad product claims unless local dependency data confirms Sentencepiece before 0.2.1.

Mitigation direction

  • Upgrade Google Sentencepiece to version 0.2.1 or later.
  • Apply relevant Red Hat advisories where Sentencepiece is supplied by Red Hat packages.
  • Restrict model-file ingestion to trusted sources and controlled build pipelines.
  • Review vendor guidance for downstream products that bundle Sentencepiece.
  • Reject or quarantine unexpected Sentencepiece model files from untrusted users.

Validation and detection

  • Inventory direct and transitive Sentencepiece versions across applications and ML environments.
  • Confirm no deployed package remains below Sentencepiece 0.2.1.
  • Identify workflows that load external or user-supplied model files.
  • Check Red Hat errata applicability for affected enterprise systems.
  • Verify production pipelines only consume approved model artifacts.
Prepared
Confidence
medium
Sources
8

Public sources used

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-119: 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-1260 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
High
CVSS
8.5 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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.

2CVSS vectors
5Timeline events
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

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
8.5CVSS 4.0HighCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——Google
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9redhat-SADP

Vulnerability scoring details

Base CVSS 4.0 score

8.5High
CVSS 4.0 vector shape for CVE-2026-1260Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
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. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

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

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPsentencepiece: Sentencepiece: Invalid memory access leading to potential arbitrary code execution via a crafted model file.
other:Red Hat severity ratingcvssV3_1
  • 2026-01-22T18:00:55.604Z: Reported to Red Hat.
  • 2026-01-22T17:06:17.340Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleSentencepieceAll versions prior to 0.2.1unaffected
Weakness

CWE details

CWE-119

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

CWE-119 · source CWE mapping

Improper Restriction of Operations within the Bounds of a Memory Buffer

Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs