CVE-2026-101353: Arbitrary file creation through embedded HSQLDB databases
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Someone with local access to the system can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- Fixed version: The Document Foundation LibreOffice < 26.2.7, < 26.8.2.
Low priority for now. Upgrade to The Document Foundation LibreOffice < 26.2.7, < 26.8.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
LibreOffice Base documents can contain an embedded HSQLDB database, and other documents can use such a database as a data source. The definition of the database in a crafted document could make the database engine create or write files at locations outside the document, chosen by the document. In fixed versions the files of an embedded database are kept in a private location, and an embedded database cannot create table files anywhere else.
- Published
- Nov 16, 2026
- Updated
- Nov 16, 2026
- EPSS
- —
- CWE
- CWE-73
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
CNA vs NVD score
- NVD
- —
- CNA · Document Fdn.
- 6.8
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Document Fdn.). Independent of NVD's CPE analysis and usually ahead of it.
The Document Foundation LibreOffice
- 26.2 and later · before < 26.2.7affected · 26.2 series
- 26.8 and later · before < 26.8.2affected · 26.8 series
Same product
the document foundation: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-84443Base document events run macros without the macro security check34Monitor
- CVE-2026-104920Remote Java code loaded through Calc data links34Monitor
- CVE-2026-104692Code execution through Java method calls in HSQLDB databases34Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-101351Nov 16, 2026 · Uninitialized memory used as image data in PICT import7Monitor
- ← EarlierCVE-2026-101352Nov 16, 2026 · Macros run from a document's own shortcuts, menus and toolbars34Monitor
- Later →CVE-2026-101892Nov 16, 2026 · Code execution through form control import in ODF documents34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| The Document Foundation LibreOffice | < 26.2.7 | Vendor (CNA) |
| The Document Foundation LibreOffice | < 26.8.2 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 16, 2026same day
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- truff working with TrendAI Zero Day Initiativefinder
- Thomas Rinsma and Edoardo GeraciCodean Labsfinder
- Caolán McNamaraCollabora Productivityremediation developer
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-73 · External Control of File Name or PathCVSS vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Leverage Alternate EncodingCAPEC-267likelihood: High · High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- URL EncodingCAPEC-72likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
- Using UTF-8 Encoding to Bypass Validation LogicCAPEC-80likelihood: High · High
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.