CVE-2026-1978: A vulnerability was detected in kalyan02 NanoCMS up to 0.4

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

nanocms: upgrade to newer than 0.4. Exact commands for each OS are on this page.

Q: Is CVE-2026-1978 being exploited?

CVE-2026-1978 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-1978 affect?

CVE-2026-1978 affects nanocms. Severity is medium (CVSS 5.3). A vulnerability was detected in kalyan02 NanoCMS up to 0.4. Affected by this issue is some unknown functionality of the file /data/pagesdata.txt of the component User Information Handler. Performing a manipulation results in direct request.

Q: How urgent is CVE-2026-1978?

Priority 33/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.3REMOTEUPGRADE

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

A vulnerability was detected in kalyan02 NanoCMS up to 0.4. Affected by this issue is some unknown functionality of the file /data/pagesdata.txt of the component User Information Handler. Performing a manipulation results in direct request. It is possible to initiate the attack remotely. The exploit is now public and may be used. You should change the configuration settings.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 64%)
CISA exploited list	No
Weakness	CWE-425
Published	2026-02-06
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: kalyan02

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 05:16 UTCPublished CVE record published
2026-06-17 10:16 UTCUpdated Record last modified

kalyan02 nanocms UPGRADE

Affected: <= 0.4

Fixed in: newer than 0.4

Safe to downgrade to: no unaffected older release

1. Check installed version

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

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

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade nanocms

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-1978?

nanocms: upgrade to newer than 0.4. Exact commands for each OS are on this page.

Is CVE-2026-1978 being exploited?

CVE-2026-1978 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-1978 affect?

CVE-2026-1978 affects nanocms. Severity is medium (CVSS 5.3). A vulnerability was detected in kalyan02 NanoCMS up to 0.4. Affected by this issue is some unknown functionality of the file /data/pagesdata.txt of the component User Information Handler. Performing a manipulation results in direct request.

How urgent is CVE-2026-1978?

Priority 33/100. Remotely exploitable, no login, no user action

Related CVEs

CVE-2022-50898 HIGH 8.8 DOWNGRADE NanoCMS 0.4 contains an authenticated file upload vulnerability that allows remote code execution through unva

References

← Back to latest CVEs