Debian Fixes LibreOffice dBASE File Code Execution Vulnerability

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

Inventory LibreOffice on Debian 13 trixie and install 4:25.2.3-2+deb13u9 from the supported security repository. Restart desktop sessions or document-processing services as needed, verify active versions and normal file workflows, and retain package and test evidence.

Confirm Scope And Apply The Supported Remediation

What to do now: Record Debian release, installed LibreOffice package versions, desktop users, automated document conversion services, container images and accountable owners. Prioritize workflows that open or convert untrusted dBASE database files. Match the installed Debian package to the trixie advisory; assess separately bundled, Flatpak or other distribution builds through their own supported channels. Upgrade the LibreOffice packages through the supported Debian security repository. Close and restart affected applications or restart the relevant document-processing service so it uses the updated code. Debian lists no workaround as a substitute for the package update. Verify the installed package build and active processes. Test normal document opening, database import and automated conversion workflows used by the organization. Retain package-manager output, restart records, deployment identifiers and regression-test results.

Open the authoritative advisory

Last verified: 2026-11-08 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeLibreOffice packages on Debian 13 trixie
AdvisoryDSA-6615-1
CVECVE-2026-76181
Authoritative release dateNovember 7, 2026 at 19:30:46 UTC, as stated in the Debian advisory mailing-list message.
Authority revision dateNo later revision is stated in the captured Debian advisory.
Affected versionsDebian stable (trixie) LibreOffice packages covered by DSA-6615-1 before the fixed Debian build. The advisory does not state a complete upstream LibreOffice version range.
Fixed versionlibreoffice 4:25.2.3-2+deb13u9 for Debian trixie
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusThe Debian advisory does not confirm malicious exploitation.; no exploitation claim is inferred.

What Changed

Debian released DSA-6615-1 for a buffer overflow while processing dBASE database files in LibreOffice. A crafted file could potentially cause arbitrary code execution.

What To Validate Now

  1. Inventory. Record Debian release, installed LibreOffice package versions, desktop users, automated document conversion services, container images and accountable owners.
  2. Establish applicability. Prioritize workflows that open or convert untrusted dBASE database files. Match the installed Debian package to the trixie advisory; assess separately bundled, Flatpak or other distribution builds through their own supported channels.
  3. Remediate. Upgrade the LibreOffice packages through the supported Debian security repository. Close and restart affected applications or restart the relevant document-processing service so it uses the updated code. Debian lists no workaround as a substitute for the package update.
  4. Validate. Verify the installed package build and active processes. Test normal document opening, database import and automated conversion workflows used by the organization. Retain package-manager output, restart records, deployment identifiers and regression-test results.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

The Debian package version includes the 4: epoch; compare the complete package version. Coordinate application restarts to avoid losing unsaved work. This advisory does not establish that a particular customer opened a malicious file or was compromised.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.