Vulnerability Database · Go · Package report

github.com/google/flatbuffers: vulnerability history, versions and safety

github.com/google/flatbuffers is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/google/flatbuffers v25.12.19+incompatible i

Updated on 23 Oct 2026

Good news: v25.12.19+incompatible, the version you would install today, has no known vulnerabilities.

Package health score 87/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on v25.12.19+incompatible or newer. This can change: a vulnerability disclosed tomorrow can affect v25.12.19+incompatible too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v25.12.19+incompatible — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 26,569 i
  • OpenSSF scorecard 5/10 i
  • Last release 10 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/google/flatbuffers, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.0.0-20261021203751-6dda43bbaa99 21 Oct 2026 none Apache-2.0 — Details →
v25.12.20-0.20261021203751-6dda43bbaa99+incompatible 21 Oct 2026 none Apache-2.0 — Details →
v0.0.0-20260914180213-b8431fbcd7a5 14 Sep 2026 none Apache-2.0 — Details →
v25.12.20-0.20260914180213-b8431fbcd7a5+incompatible 14 Sep 2026 none Apache-2.0 — Details →
v0.0.0-20260811194944-5761d6e67af8 11 Aug 2026 none Apache-2.0 — Details →
v25.12.20-0.20260811194944-5761d6e67af8+incompatible 11 Aug 2026 none Apache-2.0 — Details →
v0.0.0-20260618132353-81edeb17d911 18 Jun 2026 none Apache-2.0 — Details →
v25.12.20-0.20260618132353-81edeb17d911+incompatible 18 Jun 2026 none Apache-2.0 — Details →
v0.0.0-20260618095924-5982eb6495cc 18 Jun 2026 none Apache-2.0 — Details →
v25.12.20-0.20260618095924-5982eb6495cc+incompatible 18 Jun 2026 none Apache-2.0 — Details →
v0.0.0-20260525011342-38df29380a97 25 May 2026 none Apache-2.0 — Details →
v25.12.20-0.20260525011342-38df29380a97+incompatible 25 May 2026 none Apache-2.0 — Details →
v0.0.0-20260508081610-1f438bd40f3f 08 May 2026 none Apache-2.0 — Details →
v25.12.20-0.20260508081610-1f438bd40f3f+incompatible 08 May 2026 none Apache-2.0 — Details →
v0.0.0-20260508014941-392165432ac4 08 May 2026 none Apache-2.0 — Details →
v25.12.20-0.20260508014941-392165432ac4+incompatible 08 May 2026 none Apache-2.0 — Details →
v0.0.0-20260506023953-e6bbb3d22e9e 06 May 2026 none Apache-2.0 — Details →
v25.12.20-0.20260506023953-e6bbb3d22e9e+incompatible 06 May 2026 none Apache-2.0 — Details →
v0.0.0-20260505021130-a6979fe14adf 05 May 2026 none Apache-2.0 — Details →
v25.12.20-0.20260505021130-a6979fe14adf+incompatible 05 May 2026 none Apache-2.0 — Details →
v0.0.0-20260418003006-bab10754d93d 18 Apr 2026 none Apache-2.0 — Details →
v25.12.20-0.20260418003006-bab10754d93d+incompatible 18 Apr 2026 none Apache-2.0 — Details →
v0.0.0-20260417205003-d6444fb7fc73 17 Apr 2026 none Apache-2.0 — Details →
v25.12.20-0.20260417205003-d6444fb7fc73+incompatible 17 Apr 2026 none Apache-2.0 — Details →
v0.0.0-20260403141208-e223d69b3657 03 Apr 2026 none Apache-2.0 — Details →
v25.12.20-0.20260403141208-e223d69b3657+incompatible 03 Apr 2026 none Apache-2.0 — Details →
v0.0.0-20260402101427-05cc7a2eff68 02 Apr 2026 none Apache-2.0 — Details →
v25.12.20-0.20260402101427-05cc7a2eff68+incompatible 02 Apr 2026 none Apache-2.0 — Details →
v0.0.0-20260402080303-8a12183c3bf2 02 Apr 2026 none Apache-2.0 — Details →
v25.12.20-0.20260402080303-8a12183c3bf2+incompatible 02 Apr 2026 none Apache-2.0 — Details →
v0.0.0-20260330123224-3860f1cf7f13 30 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260330123224-3860f1cf7f13+incompatible 30 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260323172803-4e582b0c1d60 23 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260323172803-4e582b0c1d60+incompatible 23 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260320020145-8396e00dd876 20 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260320020145-8396e00dd876+incompatible 20 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260319123637-22770f7e851c 19 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260319123637-22770f7e851c+incompatible 19 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260319025446-93f587a6d30c 19 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260319025446-93f587a6d30c+incompatible 19 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260319020123-8afb68f074b9 19 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260317165826-2e07f269b955 17 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260317165826-2e07f269b955+incompatible 17 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260312134432-10c994155ca8 12 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260312134432-10c994155ca8+incompatible 12 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260312022332-fc9909c30a85 12 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260312022332-fc9909c30a85+incompatible 12 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260311152623-9e3fe5d3f6ec 11 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260311152623-9e3fe5d3f6ec+incompatible 11 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260311024246-dc9217347eb9 11 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260311021521-a7fed2ce67a2 11 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260311021521-a7fed2ce67a2+incompatible 11 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260309034307-8aa7084f016e 09 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260309034307-8aa7084f016e+incompatible 09 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260307131934-0f469cad5426 07 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260307131934-0f469cad5426+incompatible 07 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260307031854-72e51c61f73b 07 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260307031854-72e51c61f73b+incompatible 07 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260306204958-24c2432d9949 06 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260306192032-292870612c9d 06 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260306192032-292870612c9d+incompatible 06 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260305140455-57659d9f380a 05 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260305140455-57659d9f380a+incompatible 05 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260305024946-08b6372a36b1 05 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260305024946-08b6372a36b1+incompatible 05 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260305023659-c13c3bf95608 05 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260305022853-47eeb8f4e95c 05 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260305021545-e7c6874192a6 05 Mar 2026 none Apache-2.0 — Details →
v25.12.20-0.20260305021545-e7c6874192a6+incompatible 05 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20260223075537-94d6b8086b46 23 Feb 2026 none Apache-2.0 — Details →
v25.12.20-0.20260223075537-94d6b8086b46+incompatible 23 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260219010946-fa709636b482 19 Feb 2026 none Apache-2.0 — Details →
v25.12.20-0.20260219010946-fa709636b482+incompatible 19 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260217092232-b8e3d215b866 17 Feb 2026 none Apache-2.0 — Details →
v25.12.20-0.20260217092232-b8e3d215b866+incompatible 17 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260212184221-d71c0ab4accd 12 Feb 2026 none Apache-2.0 — Details →
v25.12.20-0.20260212184221-d71c0ab4accd+incompatible 12 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260207080422-c21bda16493f 07 Feb 2026 none Apache-2.0 — Details →
v25.12.20-0.20260207080422-c21bda16493f+incompatible 07 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260205175700-03fffb25e2d7 05 Feb 2026 none Apache-2.0 — Details →
v25.12.19-2026-02-06-03fffb2+incompatible 05 Feb 2026 none Apache-2.0 — Details →
v25.12.20-0.20260205175700-03fffb25e2d7+incompatible 05 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260204231332-1a7495a6dd58 04 Feb 2026 none Apache-2.0 — Details →
v25.12.20-0.20260204231332-1a7495a6dd58+incompatible 04 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260204154319-3c1bb67ae10d 04 Feb 2026 none Apache-2.0 — Details →
v25.12.20-0.20260204154319-3c1bb67ae10d+incompatible 04 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260204152818-5b9de8b6c0d2 04 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260204151505-ea0a73d1683c 04 Feb 2026 none Apache-2.0 — Details →
v25.12.20-0.20260204151505-ea0a73d1683c+incompatible 04 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260204141250-9c2c56dc6ae2 04 Feb 2026 none Apache-2.0 — Details →
v25.12.20-0.20260204141250-9c2c56dc6ae2+incompatible 04 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260204133455-e5a9ff757f94 04 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260204130508-e53732b9b984 04 Feb 2026 none Apache-2.0 — Details →
v25.12.20-0.20260204130508-e53732b9b984+incompatible 04 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260204125149-b84b676c89c1 04 Feb 2026 none Apache-2.0 — Details →
v25.12.20-0.20260204123741-3211f857d13f+incompatible 04 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260121010120-af8997b567a9 21 Jan 2026 none Apache-2.0 — Details →
v25.12.20-0.20260121010120-af8997b567a9+incompatible 21 Jan 2026 none Apache-2.0 — Details →
v0.0.0-20251222022514-8914d06ab712 22 Dec 2025 none Apache-2.0 — Details →
v25.12.20-0.20251222022514-8914d06ab712+incompatible 22 Dec 2025 none Apache-2.0 — Details →
v0.0.0-20251222001034-522f2379a6a5 22 Dec 2025 none — — Details →
v25.12.20-0.20251222001034-522f2379a6a5+incompatible 22 Dec 2025 none — — Details →
v0.0.0-20251221202530-9d64b9c0c042 21 Dec 2025 none — — Details →
v25.12.20-0.20251221202530-9d64b9c0c042+incompatible 21 Dec 2025 none — — Details →
v0.0.0-20251221191805-d01f20f2fbcc 21 Dec 2025 none — — Details →
v25.12.20-0.20251221191805-d01f20f2fbcc+incompatible 21 Dec 2025 none — — Details →
v0.0.0-20251219230607-7e163021e59c 19 Dec 2025 none — — Details →
v25.12.19+incompatible 19 Dec 2025 none — — Details →
v0.0.0-20251219011433-f74fda299dba 19 Dec 2025 none — — Details →
v25.9.24-0.20251219011433-f74fda299dba+incompatible 19 Dec 2025 none — — Details →
v0.0.0-20251219010350-15802fa26c83 19 Dec 2025 none — — Details →
v0.0.0-20251214235917-a86afae9399b 14 Dec 2025 none — — Details →
v25.9.24-0.20251214235917-a86afae9399b+incompatible 14 Dec 2025 none — — Details →
v0.0.0-20251214215927-7bfaabc3587c 14 Dec 2025 none — — Details →
v25.9.24-0.20251214215927-7bfaabc3587c+incompatible 14 Dec 2025 none — — Details →
v0.0.0-20251214182824-e1407e434179 14 Dec 2025 none — — Details →
v25.9.24-0.20251214182824-e1407e434179+incompatible 14 Dec 2025 none — — Details →
v0.0.0-20251213234058-c9a301e60181 13 Dec 2025 none — — Details →
v25.9.24-0.20251213234058-c9a301e60181+incompatible 13 Dec 2025 none — — Details →
v0.0.0-20251210145050-19b2300f93a5 10 Dec 2025 none — — Details →

The newest 120 of 1,303 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for github.com/google/flatbuffers

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/google/flatbuffers

Is github.com/google/flatbuffers safe to use?

Vulert has no vulnerabilities on record for github.com/google/flatbuffers in Go at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is github.com/google/flatbuffers's Vulert package health score?

Vulert scores github.com/google/flatbuffers 87/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of github.com/google/flatbuffers affected?

No. v25.12.19+incompatible, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of github.com/google/flatbuffers should I use?

v25.12.19+incompatible is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/google/flatbuffers have?

0 vulnerabilities are recorded for github.com/google/flatbuffers in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/google/flatbuffers vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/google/flatbuffers in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/google/flatbuffers are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/google/flatbuffers for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/google/flatbuffers version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.