Skip to content

LibreOffice

Bug bounty on Sorona libreoffice.org

Accepting reports open-source
Top reward
$1,500
Top severity paid
Critical
Assets in scope
10
Public CVEs
72
Last change
No changes yet

At a glance

What to know before you start testing.

Pays from $1,500
for critical bugs.
Partial safe harbor
Some legal protection; read the terms.
Publish after a fix
Coordinate the timing with the company.

Rewards

What Sorona lists as the payout for each severity.

Severity Reward
Critical $1,500+
High $700+
Medium $300+
Low $100 $100 / 1 month Claude Max
Safe harbor
Partial Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf.

Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

10 assets you may test, 6 excluded.

Web 1

  • https://www.libreoffice.org

Products and areas 9

  • Digital-signature validation for both document and macro signatures.
  • Formula parsing and compilation in Calc (for example the CVE-2026-8357 heap overflow during formula compilation) and formula/OLE handling in Writer and Math.
  • Graphics and embedded-object import filters parsed on document load, including EMF/EMF+, WMF, DXF, and SVG.
  • Legacy binary import filters, DOC, XLS, and PPT (MS Office 97-2003) plus RTF, handled through the writerfilter, oox, and filter modules.
  • Multiple concurrently maintained release lines receive fixes, including the fresh and still (LTS-style) branches such as 26.2.x and 25.8.x.
  • ODF import and parsing for ODT, ODS, and ODP, including the OpenDocument encryption and signature stack.
  • OOXML import filters for DOCX, XLSX, and PPTX, covering document and text-box parsing, deferred parser-event replay, and encryption-header handling, the suite's richest historical bug surface (for example the CVE-2026-6047 type-confusion in OOXML text-box import and the CVE-2026-4430 out-of-bounds write from an OOXML encryption salt mismatch).
  • The macro and scripting subsystem: Basic macros, document-embedded scripting, and the surrounding security controls (macro security levels, auto-execution, and event bindings).
  • URL and hyperlink handling together with password and encryption management for protected documents.
Out of scope (6)
  • Antivirus false positives or heuristic detections against LibreOffice binaries or installers.
  • Defects in bundled third-party libraries that should be attributed upstream, unless LibreOffice's own use of them is the flaw.
  • Documented, intended behavior of macros and scripting when the user explicitly enables or runs them.
  • End-of-life release branches that no longer receive security fixes.
  • Non-security functional bugs, which belong in the public Bugzilla rather than the security contact.
  • Reports that require the attacker to already hold local code execution or control of the user's configuration.

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Sorona's policy.

While testing

  • Submit through sorona.xyz.
  • Submit a clear proof of concept, including the crafted document, the affected version, and the platform when the bug is platform-dependent.
  • Test only against your own installations and files; never target other users or third-party infrastructure.
  • Report each distinct vulnerability separately with enough detail to reproduce it reliably.
  • Do not run automated fuzzing or scanning against any project-hosted service; fuzz locally and submit only triaged, exploitable results.
  • Keep findings confidential until sorona.xyz and the project confirm a fix or agree on disclosure.

Not accepted

  • Documented, intended behavior of macros and scripting when the user explicitly enables or runs them.
  • Non-security functional bugs
  • End-of-life release branches that no longer receive security fixes.
  • Defects in bundled third-party libraries that should be attributed upstream
  • Reports that require the attacker to already hold local code execution or control of the user's configuration.
  • Antivirus false positives or heuristic detections against LibreOffice binaries or installers.

Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 1 hour ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD
CVESeverityPublished
CVE-2026-4430 Medium 5.4 7 May 2026
CVE-2025-14714 Low 0.9 15 Dec 2025
CVE-2025-2866 Low 2.4 27 Apr 2025
CVE-2021-25635 Medium 5.2 21 Mar 2025
CVE-2025-1080 High 7.2 4 Mar 2025
CVE-2025-0514 High 7.2 25 Feb 2025
CVE-2024-12426 Medium 6.7 7 Jan 2025
CVE-2024-12425 Low 2.4 7 Jan 2025
CVE-2024-7788 High 7.8 17 Sep 2024
CVE-2024-6472 High 7.8 5 Aug 2024
CVE-2024-5261 Critical 10.0 25 Jun 2024
CVE-2024-3044 Medium 6.5 14 May 2024
CVE-2023-6186 High 8.3 11 Dec 2023
CVE-2023-6185 High 8.3 11 Dec 2023
CVE-2023-1183 Medium 5.0 10 Jul 2023
CVE-2023-0950 High 7.8 25 May 2023
CVE-2023-2255 Medium 5.3 25 May 2023
CVE-2022-3140 Medium 6.3 11 Oct 2022
CVE-2022-26305 High 7.5 25 Jul 2022
CVE-2022-26306 High 7.5 25 Jul 2022
CVE-2022-26307 High 8.8 25 Jul 2022
CVE-2021-25636 High 7.5 24 Feb 2022
CVE-2021-25634 High 7.5 12 Oct 2021
CVE-2021-25633 High 7.5 11 Oct 2021
CVE-2021-25631 High 8.8 3 May 2021
CVE-2018-18688 Medium 5.3 7 Jan 2021
CVE-2020-12802 Medium 5.3 8 Jun 2020
CVE-2020-12803 Medium 6.5 8 Jun 2020
CVE-2020-12801 Medium 5.3 18 May 2020
CVE-2012-5639 Medium 6.5 20 Dec 2019
CVE-2019-9853 High 7.8 27 Sep 2019
CVE-2019-9854 High 7.8 6 Sep 2019
CVE-2019-9855 Critical 9.8 6 Sep 2019
CVE-2019-9850 Critical 9.8 15 Aug 2019
CVE-2019-9851 Critical 9.8 15 Aug 2019
CVE-2019-9852 High 7.8 15 Aug 2019
CVE-2019-9848 Critical 9.8 17 Jul 2019
CVE-2019-9849 Medium 4.3 17 Jul 2019
CVE-2019-9847 High 7.8 9 May 2019
CVE-2018-16858 High 7.8 25 Mar 2019
CVE-2018-14939 Critical 9.8 5 Aug 2018
CVE-2018-10583 High 7.5 1 May 2018
CVE-2018-10120 High 7.8 16 Apr 2018
CVE-2018-10119 High 7.8 16 Apr 2018
CVE-2018-6871 Critical 9.8 9 Feb 2018
CVE-2017-14226 High 7.5 9 Sep 2017
CVE-2017-8358 Critical 9.8 30 Apr 2017
CVE-2017-7882 Critical 9.8 15 Apr 2017
CVE-2017-7870 Critical 9.8 14 Apr 2017
CVE-2016-10327 Critical 9.8 14 Apr 2017
CVE-2017-7856 Critical 9.8 14 Apr 2017
CVE-2016-4324 High 7.8 8 Jul 2016
CVE-2016-0795 High 7.8 18 Feb 2016
CVE-2016-0794 High 7.8 18 Feb 2016
CVE-2015-5214 Medium 6.8 10 Nov 2015
CVE-2015-5213 Medium 6.8 10 Nov 2015
CVE-2015-5212 Medium 6.8 10 Nov 2015
CVE-2015-4551 Medium 4.3 10 Nov 2015
CVE-2015-1774 Medium 6.8 28 Apr 2015
CVE-2014-9093 High 7.5 26 Nov 2014

Original policy

Copied from sorona.xyz on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Skip to content What this pays This project runs no bounty of its own. sorona.xyz pays you directly on qualified, reproduced findings. Severity │ sorona.xyz pays Critical │ $1,500+ High │ $700+ Medium │ $300+ Low │ $100 / 1 month Claude Max Submit a vulnerability Separately, for a merged upstream patch : $100 - $5,000 Google Patch Rewards pays this project as a Tier 2 target (it qualifies through its OSS-Fuzz integration), for a patch you land upstream and that stays merged, without reverts, for one month. It is paid for the patch, not for the report, and it is rate-limited to three submissions a month. Sanctions and territory exclusions apply. CVE history 7 Last 12 months 72 Lifetime Memory safety 28 % Code execution 24 % Parsing/validation 20 % Access control 15 % Latest advisories Loading the feed Overview LibreOffice is the widely used open-source office suite whose Writer, Calc, Impress and Draw applications parse a broad range of document formats, including OOXML, ODF and numerous legacy binary formats, making its import filters a large and historically vulnerable attack surface. The Document Foundation runs a vulnerability disclosure program through a shared security list and issues coordinated advisories, but pays no bounty of its own. Report through sorona.xyz and we pay you directly on qualified, reproduced findings, with up to 2x the base payout for hard, chained bugs. In scope OOXML import filters for DOCX, XLSX, and PPTX, covering document and text-box parsing, deferred parser-event replay, and encryption-header handling, the suite's richest historical bug surface (for example the CVE-2026-6047 type-confusion in OOXML text-box import and the CVE-2026-4430 out-of-bounds write from an OOXML encryption salt mismatch). ODF import and parsing for ODT, ODS, and ODP, including the OpenDocument encryption and signature stack. Legacy binary import filters, DOC, XLS, and PPT (MS Office 97-2003) plus RTF, handled through the writerfilter, oox, and filter modules. Graphics and embedded-object import filters parsed on document load, including EMF/EMF+, WMF, DXF, and SVG. Formula parsing and compilation in Calc (for example the CVE-2026-8357 heap overflow during formula compilation) and formula/OLE handling in Writer and Math. The macro and scripting subsystem: Basic macros, document-embedded scripting, and the surrounding security controls (macro security levels, auto-execution, and event bindings). Digital-signature validation for both document and macro signatures. URL and hyperlink handling together with password and encryption management for protected documents. Multiple concurrently maintained release lines receive fixes, including the fresh and still (LTS-style) branches such as 26.2.x and 25.8.x. Out of scope Documented, intended behavior of macros and scripting when the user explicitly enables or runs them. Non-security functional bugs, which belong in the public Bugzilla rather than the security contact. End-of-life release branches that no longer receive security fixes. Defects in bundled third-party libraries that should be attributed upstream, unless LibreOffice's own use of them is the flaw. Reports that require the attacker to already hold local code execution or control of the user's configuration. Antivirus false positives or heuristic detections against LibreOffice binaries or installers. Most-valued findings Memory-safety bugs in file-format import filters, heap and stack buffer overflow, out-of-bounds read and write, and use-after-free, triggered by opening a crafted document. Type confusion during parsing, where an object is written through the wrong type's field layout. Integer overflow that leads to undersized allocation or out-of-bounds access. Arbitrary code execution via crafted documents through formula compilation or filter parsing. Macro and scripting security-control bypass, including auto-exec, event-driven launch, and signed-macro trust bypass. Digital-signature validation bypass or spoofing (CWE-347) that makes a tampered document appear trusted. Program rules Submit through sorona.xyz. This project runs no bounty of its own; we validate, coordinate disclosure with the maintainers, and pay you directly. Submit a clear proof of concept, including the crafted document, the affected version, and the platform when the bug is platform-dependent. Test only against your own installations and files; never target other users or third-party infrastructure. Report each distinct vulnerability separately with enough detail to reproduce it reliably. Do not run automated fuzzing or scanning against any project-hosted service; fuzz locally and submit only triaged, exploitable results. Keep findings confidential until sorona.xyz and the project confirm a fix or agree on disclosure. Payout follows sorona.xyz's confirmation of a reproduced, qualified finding; chained or hard-to-exploit bugs may earn up to 2x the base. Disclosure The project's policy is coordinated disclosure, with public advisories typically issued within 30 days of a fix being available. Reporters are credited in advisories unless they ask to remain anonymous. Safe harbor Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf. You are responsible for understanding and following the laws that apply to you, wherever you are, and for staying within any scope the project has defined. Submit a vulnerability