dbcve.org
FedoraOperating system · Fedoraproject

CVE-2023-6186

HIGH · 8.8 CVSS v3.1 Published 2023-12-11
Fix available
A fix is available. Upgrade to 7.5.9 / 7.6.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Insufficient macro permission validation of The Document Foundation LibreOffice allows an attacker to execute built-in macros without warning. In affected versions LibreOffice supports hyperlinks with macro or similar built-in command targets that can be executed when activated without warning the user.

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 confidence

LibreOffice fails to properly validate macro permissions when processing hyperlinks containing macro or built-in command targets. Attackers can craft documents with hyperlinks that execute built-in macros silently when activated, bypassing user warnings and macro security controls.

MitigationUpdate to the patched LibreOffice version that properly validates macro permissions and warns users before executing macro commands from hyperlinks, or disable macro execution in LibreOffice security settings.

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
FedoraOperating system
Affected:= 38
Debian LinuxOperating system
Affected:= 11.0= 12.0
LibreofficeApplication
Affected:>= 7.5.0, < 7.5.9>= 7.6.0, < 7.6.4

CVSS 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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed LibreOffice version
    Run 'libreoffice --version' or check your package manager (rpm -q libreoffice on Fedora, dpkg -l libreoffice* on Debian)
    Affected if Version is >= 7.5.0 and < 7.5.9, or >= 7.6.0 and < 7.6.4
  2. Check LibreOffice macro security level
    Open LibreOffice, go to Tools > Options > Security > Macro Security. Verify if the security level is set to 'Very High' which blocks all macros, or 'High' which prompts before running macros from untrusted sources
    Affected if Macro security is set to 'Medium' or 'Low', allowing macros to run with minimal or no prompting
  3. Inspect documents for hyperlink-based macro triggers
    Open the document in LibreOffice, right-click hyperlinks, and examine the URL field. Look for hyperlinks starting with 'macro:', '.uno:', or other internal LibreOffice commands
    Affected if Document contains hyperlinks with macro: or .uno: protocols pointing to internal commands
  4. Verify macro execution settings in trusted locations
    Go to Tools > Options > Security > Macro Security > Trusted Locations. Check if any locations are marked as trusted for macro execution
    Affected if Documents are stored in or loaded from trusted locations, allowing macros to run without prompts

You are affected if LibreOffice version falls within the vulnerable ranges AND macro security settings allow automatic execution of macros from hyperlinks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.5.9 / 7.6.4 or later
Fixed in 7.5.97.6.4
Interim mitigation

Update to the patched LibreOffice version that properly validates macro permissions and warns users before executing macro commands from hyperlinks, or disable macro execution in LibreOffice security settings.

Recommended fix High confidence

LibreOffice 7.5.9+ or 7.6.4+

  1. Update LibreOffice to version 7.5.9 or later for the 7.5.x branch, or 7.6.4 or later for the 7.6.x branch
  2. On Fedora 38, run: sudo dnf update libreoffice
  3. On Debian 11.0 or 12.0, run: sudo apt update && sudo apt upgrade libreoffice
  4. Verify the installed version matches or exceeds the fixed release (e.g., libreoffice --version)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fedora Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6186 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6186 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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