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 hit invalid memory access when it loads a specially vulnerable model file. The file is not produced by normal training, so risk is highest where applications accept or distribute untrusted model files. The issue is rated high because successful triggering can affect confidentiality, integrity, and availability.

Executive priority

Treat as a high-priority dependency and model-supply-chain issue for AI and NLP systems, especially where model files cross trust boundaries. Patch during the next urgent security cycle and tighten model provenance controls.

Technical view

CVE-2026-1260 affects Google SentencePiece before 0.2.1. The source describes CWE-119 invalid memory access triggered by use of a vulnerable model file. CVSS 4.0 is 8.5 with local attack vector, low complexity, no privileges, and passive user interaction.

Likely exposure

Organizations are exposed if they run SentencePiece before 0.2.1, including through packaged dependencies, and load model files from users, partners, downloads, or model registries. Exposure is lower for systems using only internally generated models from normal training procedures.

Exploitation context

The provided sources do not show active exploitation, and KEV is false. Exploitation appears to require getting a vulnerable model file loaded by SentencePiece, not direct remote network access. Evidence on public exploit availability is not provided.

Researcher notes

Key constraint is the model-file precondition: sources state the vulnerable file is not created by normal training. Validate reachable parser paths and package provenance, but do not assume network exploitability or active exploitation without additional evidence.

Mitigation direction

  • Upgrade SentencePiece to 0.2.1 or a vendor package that includes the fix.
  • For Red Hat systems, review RHSA-2026:3713 and RHSA-2026:3782 package status.
  • Restrict SentencePiece model files to trusted, controlled sources.
  • Quarantine externally supplied model files until vendor guidance and validation are complete.
  • Check application dependency locks and container images for embedded older SentencePiece versions.

Validation and detection

  • Inventory direct and transitive SentencePiece use across applications, images, and ML pipelines.
  • Confirm installed versions are 0.2.1 or vendor-fixed builds.
  • Identify workflows that load externally supplied SentencePiece model files.
  • Review model registry provenance and access controls for SentencePiece assets.
  • Use vendor advisories to verify affected package names and fixed versions.
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