CVE-2026-2016: A security vulnerability has been detected in happyfish100 libfastcommon up to 1.0.84

Q: How do I fix CVE-2026-2016?

libfastcommon: upgrade to newer than 1.0.84. Exact commands for each OS are on this page.

Q: Is CVE-2026-2016 being exploited?

CVE-2026-2016 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-2016 affect?

CVE-2026-2016 affects libfastcommon. Severity is medium (CVSS 5.3). A security vulnerability has been detected in happyfish100 libfastcommon up to 1.0.84. Affected by this vulnerability is the function base64_decode of the file src/base64.c. The manipulation leads to stack-based buffer overflow. Local acces

Q: How urgent is CVE-2026-2016?

Priority 29/100. Public exploit reference

Routine

MEDIUM 5.3UPGRADE

CVE-2026-2016 is a medium-severity flaw (CVSS 5.3) affecting libfastcommon. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A security vulnerability has been detected in happyfish100 libfastcommon up to 1.0.84. Affected by this vulnerability is the function base64_decode of the file src/base64.c. The manipulation leads to stack-based buffer overflow. Local access is required to approach this attack. The exploit has been disclosed publicly and may be used. The identifier of the patch is 82f66af3e252e3e137dba0c3891570f085e79adf. Applying a patch is the recommended actio

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 78%)
CISA exploited list	No
Weakness	CWE-119, CWE-121, CWE-787
Published	2026-02-06
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: happyfish100

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-02-06 12:16 UTCPublished CVE record published
2026-06-17 10:30 UTCUpdated Record last modified

happyfish100 libfastcommon UPGRADE

Affected: <= 1.0.84

Fixed in: newer than 1.0.84

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy libfastcommon || rpm -q libfastcommon || libfastcommon --version

2. UPGRADE to newer than 1.0.84 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libfastcommon

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libfastcommon

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-2016?

libfastcommon: upgrade to newer than 1.0.84. Exact commands for each OS are on this page.

Is CVE-2026-2016 being exploited?

CVE-2026-2016 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-2016 affect?

CVE-2026-2016 affects libfastcommon. Severity is medium (CVSS 5.3). A security vulnerability has been detected in happyfish100 libfastcommon up to 1.0.84. Affected by this vulnerability is the function base64_decode of the file src/base64.c. The manipulation leads to stack-based buffer overflow. Local acces

How urgent is CVE-2026-2016?

Priority 29/100. Public exploit reference

References

← Back to latest CVEs