CVE-2020-36623: A vulnerability was found in Pengu

Q: How do I fix CVE-2020-36623?

pengu: upgrade to 2020-11-02. Exact commands for each OS are on this page.

Q: Is CVE-2020-36623 being exploited?

CVE-2020-36623 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-2020-36623 affect?

CVE-2020-36623 affects pengu. Severity is medium (CVSS 4.3). A vulnerability was found in Pengu. It has been declared as problematic. Affected by this vulnerability is the function runApp of the file src/index.js. The manipulation leads to cross-site request forgery. The attack can be launched remote

Q: How urgent is CVE-2020-36623?

Priority 20/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2020-36623 is a medium-severity flaw (CVSS 4.3) affecting pengu. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability was found in Pengu. It has been declared as problematic. Affected by this vulnerability is the function runApp of the file src/index.js. The manipulation leads to cross-site request forgery. The attack can be launched remotely. The name of the patch is aea66f12b8cdfc3c8c50ad6a9c89d8307e9d0a91. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-216475.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 78%)
CISA exploited list	No
Weakness	CWE-863, CWE-352
Published	2022-12-21
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: pengu project

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

Am I affected?

Timeline

2022-12-21 19:15 UTCPublished CVE record published
2026-06-17 03:15 UTCUpdated Record last modified

pengu project pengu UPGRADE

Affected: < 2020-11-02

Fixed in: 2020-11-02

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 2020-11-02 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pengu

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-2020-36623?

pengu: upgrade to 2020-11-02. Exact commands for each OS are on this page.

Is CVE-2020-36623 being exploited?

CVE-2020-36623 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-2020-36623 affect?

CVE-2020-36623 affects pengu. Severity is medium (CVSS 4.3). A vulnerability was found in Pengu. It has been declared as problematic. Affected by this vulnerability is the function runApp of the file src/index.js. The manipulation leads to cross-site request forgery. The attack can be launched remote

How urgent is CVE-2020-36623?

Priority 20/100. No elevated risk signals yet.

References

← Back to latest CVEs