VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

boringssl: vulnerability history, versions and safety

boringssl is a package in the OSS-Fuzz ecosystem. Vulert records 6 vulnerabilities for it across 4 releases, from Jan 2021 to May 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded M5 L1
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.

See all boringssl vulnerabilities

Vulert verdict on boringssl i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 05 May 2024. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 6 vulnerabilities on record across 3 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 6 over 3 years · 0 in the last year i
  • Latest disclosure 05 May 2024 i
  • Highest CVSS n/a i
  • With no published fix 0 i

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 holds for boringssl, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
fips-20190808 M1 Yes Details →
fips-20180730 M1 Yes Details →
fips-android-20191020 M1 Yes Details →
version_for_cocoapods_10.0 M1 Yes Details →

Newest 4 of 4 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2023 1
  • 2024 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 6 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for boringssl

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Use-of-uninitialized-value in bn_sub_words in boringssl N/A medium f8f35c95550e6796ab8b2c0f8e37e7ce4bc67302 13 Jan 2021
Heap-buffer-overflow in parse_sigalgs_list in BoringSSL N/A medium ddedf6d455e33d6a0b3bc40581700f3d252029d7 13 Jan 2021
Heap-use-after-free in sk_num in BoringSSL N/A low 507ac830036d7531489490831814cf03e0d7c4d6 02 Feb 2023
Use-of-uninitialized-value in bssl::ssl_cipher_process_rulestr N/A medium 3e89a7e8db8139db356b892ca9993172346c80cf 05 May 2024
Use-of-uninitialized-value in boringssl: ssl_str_to_group_ids N/A medium 3e89a7e8db8139db356b892ca9993172346c80cf 05 May 2024

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 boringssl

Is boringssl safe to use?

Vulert records 6 vulnerabilities for boringssl in OSS-Fuzz: 0 critical, 0 high, 5 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does boringssl have?

6 vulnerabilities are recorded for boringssl in the OSS-Fuzz ecosystem: 0 critical, 0 high, 5 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new boringssl vulnerabilities disclosed?

0 vulnerabilities were recorded for boringssl in the last 12 months, and the oldest entry in this database dates to 13 Jan 2021. 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 boringssl 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 boringssl for upcoming vulnerabilities?

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