WID-SEC-W-2026-4591
Vulnerability from csaf_certbund - Published: 2026-11-16 23:00 - Updated: 2026-11-16 23:00| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source LibreOffice <26.2.7
Open Source / LibreOffice
|
<26.2.7 | ||
|
Open Source LibreOffice <26.8.2
Open Source / LibreOffice
|
<26.8.2 |
{
"document": {
"aggregate_severity": {
"text": "mittel"
},
"category": "csaf_base",
"csaf_version": "2.0",
"distribution": {
"tlp": {
"label": "WHITE",
"url": "https://www.first.org/tlp/"
}
},
"lang": "de-DE",
"notes": [
{
"category": "legal_disclaimer",
"text": "Das BSI ist als Anbieter f\u00fcr die eigenen, zur Nutzung bereitgestellten Inhalte nach den allgemeinen Gesetzen verantwortlich. Nutzerinnen und Nutzer sind jedoch daf\u00fcr verantwortlich, die Verwendung und/oder die Umsetzung der mit den Inhalten bereitgestellten Informationen sorgf\u00e4ltig im Einzelfall zu pr\u00fcfen."
},
{
"category": "description",
"text": "LibreOffice ist eine leistungsf\u00e4hige Office-Suite, voll kompatibel mit den Programmen anderer gro\u00dfer Office-Anbieter, f\u00fcr verbreitete Betriebssysteme wie Windows, GNU/Linux und Apple Mac OS X geeignet. LibreOffice bietet sechs Anwendungen f\u00fcr die Erstellung von Dokumenten und zur Datenverarbeitung: Writer, Calc, Impress, Draw, Base und Math.",
"title": "Produktbeschreibung"
},
{
"category": "summary",
"text": "Ein Angreifer kann mehrere Schwachstellen in LibreOffice ausnutzen, um Informationen offenzulegen, beliebigen Programmcode auszuf\u00fchren, Sicherheitsma\u00dfnahmen zu umgehen, Dateien zu manipulieren oder eine Speicherbesch\u00e4digung zu verursachen. F\u00fcr eine erfolgreiche Ausnutzung ist eine Benutzerinteraktion erforderlich.",
"title": "Angriff"
},
{
"category": "general",
"text": "- Linux\n- MacOS X\n- Windows",
"title": "Betroffene Betriebssysteme"
}
],
"publisher": {
"category": "other",
"contact_details": "csaf-provider@cert-bund.de",
"name": "Bundesamt f\u00fcr Sicherheit in der Informationstechnik",
"namespace": "https://www.bsi.bund.de"
},
"references": [
{
"category": "self",
"summary": "WID-SEC-W-2026-4591 - CSAF Version",
"url": "https://wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-4591.json"
},
{
"category": "self",
"summary": "WID-SEC-2026-4591 - Portal Version",
"url": "https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4591"
},
{
"category": "external",
"summary": "LibreOffice Security Advisories vom 2026-11-16",
"url": "https://www.libreoffice.org/security/"
}
],
"source_lang": "en-US",
"title": "LibreOffice: Mehrere Schwachstellen",
"tracking": {
"current_release_date": "2026-11-16T23:00:00.000+00:00",
"generator": {
"date": "2026-11-17T11:12:02.385+00:00",
"engine": {
"name": "BSI-WID",
"version": "1.7.0"
}
},
"id": "WID-SEC-W-2026-4591",
"initial_release_date": "2026-11-16T23:00:00.000+00:00",
"revision_history": [
{
"date": "2026-11-16T23:00:00.000+00:00",
"number": "1",
"summary": "Initiale Fassung"
}
],
"status": "final",
"version": "1"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version_range",
"name": "\u003c26.2.7",
"product": {
"name": "Open Source LibreOffice \u003c26.2.7",
"product_id": "T063198"
}
},
{
"category": "product_version",
"name": "26.2.7",
"product": {
"name": "Open Source LibreOffice 26.2.7",
"product_id": "T063198-fixed",
"product_identification_helper": {
"cpe": "cpe:/a:libreoffice:libreoffice:26.2.7"
}
}
},
{
"category": "product_version_range",
"name": "\u003c26.8.2",
"product": {
"name": "Open Source LibreOffice \u003c26.8.2",
"product_id": "T063199"
}
},
{
"category": "product_version",
"name": "26.8.2",
"product": {
"name": "Open Source LibreOffice 26.8.2",
"product_id": "T063199-fixed",
"product_identification_helper": {
"cpe": "cpe:/a:libreoffice:libreoffice:26.8.2"
}
}
}
],
"category": "product_name",
"name": "LibreOffice"
}
],
"category": "vendor",
"name": "Open Source"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2026-100101",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-100101"
},
{
"cve": "CVE-2026-101351",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-101351"
},
{
"cve": "CVE-2026-101352",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-101352"
},
{
"cve": "CVE-2026-101353",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-101353"
},
{
"cve": "CVE-2026-101892",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-101892"
},
{
"cve": "CVE-2026-101929",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-101929"
},
{
"cve": "CVE-2026-101930",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-101930"
},
{
"cve": "CVE-2026-101933",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-101933"
},
{
"cve": "CVE-2026-104007",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-104007"
},
{
"cve": "CVE-2026-104692",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-104692"
},
{
"cve": "CVE-2026-104920",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-104920"
},
{
"cve": "CVE-2026-104933",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-104933"
},
{
"cve": "CVE-2026-108169",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-108169"
},
{
"cve": "CVE-2026-18563",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-18563"
},
{
"cve": "CVE-2026-84443",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-84443"
},
{
"cve": "CVE-2026-97892",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-97892"
},
{
"cve": "CVE-2026-97894",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-97894"
},
{
"cve": "CVE-2026-97999",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-97999"
},
{
"cve": "CVE-2026-98100",
"product_status": {
"known_affected": [
"T063198",
"T063199"
]
},
"release_date": "2026-11-16T23:00:00.000+00:00",
"title": "CVE-2026-98100"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.