CVE-2026-1260
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInvalid 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA memory access vulnerability exists in Sentencepiece versions prior to 0.2.1. The flaw is triggered when parsing a specially crafted model file that cannot be generated through normal training procedures, leading to invalid memory access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Sentencepiece library versionRun 'pip show sentencepiece' or check your package manager for the installed sentencepiece versionAffected if The installed version is below 0.2.1
-
Identify Sentencepiece library version programmaticallyIn Python, run 'import sentencepiece as sp; print(sp.__version__)' or check the library's version attributeAffected if The version returned is less than 0.2.1
-
Determine model file sourceReview the origin of any .model files being loaded with sentencepiece.SentencePieceProcessor.Load() or LoadModel()Affected if The model file was obtained from an untrusted or non-standard source, or was not created through normal training procedures
-
Inspect model loading behaviorMonitor application logs or error output when loading model files with sentencepieceAffected if Loading a model file from an untrusted source triggers unexpected behavior, crashes, or memory errors
You are affected if you have sentencepiece version below 0.2.1 AND load model files from untrusted or non-standard sources that could be specifically crafted to exploit this flaw.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.2.1
Upgrade Sentencepiece to version 0.2.1 or later. Additionally, ensure only model files from trusted, legitimate training procedures are loaded.
Sentencepiece >= 0.2.1
- Upgrade Sentencepiece to version 0.2.1 or later to remediate the memory buffer bounds error
- If using a package manager (e.g., pip, conda), run: pip install sentencepiece>=0.2.1 or conda install sentencepiece>=0.2.1
- After upgrading, re-validate any model files in use to ensure they were not crafted to exploit this vulnerability
- If using Sentencepiece in a larger project, rebuild or update dependencies to pull in the fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1260 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1260 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data