CVE-2019-25091: A vulnerability classified as problematic has been found in nsupdate.info

Q: How do I fix CVE-2019-25091?

nsupdate.info: upgrade to 2019-05-19. Exact commands for each OS are on this page.

Q: Is CVE-2019-25091 being exploited?

CVE-2019-25091 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-2019-25091 affect?

CVE-2019-25091 affects nsupdate.info. Severity is low (CVSS 3.7). A vulnerability classified as problematic has been found in nsupdate.info. This affects an unknown part of the file src/nsupdate/settings/base.py of the component CSRF Cookie Handler. The manipulation of the argument CSRF_COOKIE_HTTPONLY le

Q: How urgent is CVE-2019-25091?

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

Routine

LOW 3.7REMOTEUPGRADE

CVE-2019-25091 is a low-severity flaw (CVSS 3.7) affecting nsupdate.info. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability classified as problematic has been found in nsupdate.info. This affects an unknown part of the file src/nsupdate/settings/base.py of the component CSRF Cookie Handler. The manipulation of the argument CSRF_COOKIE_HTTPONLY leads to cookie without 'httponly' flag. It is possible to initiate the attack remotely. The name of the patch is 60a3fe559c453bc36b0ec3e5dd39c1303640a59a. It is recommended to apply a patch to fix this issue. Th

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	3.7 (Low)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 48%)
CISA exploited list	No
Weakness	CWE-1004
Published	2022-12-27
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: nsupdate

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

Am I affected?

Timeline

2022-12-27 23:15 UTCPublished CVE record published
2026-06-17 02:31 UTCUpdated Record last modified

nsupdate nsupdate.info UPGRADE

Affected: < 2019-05-19

Fixed in: 2019-05-19

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy nsupdate.info || rpm -q nsupdate.info || nsupdate.info --version

2. UPGRADE to 2019-05-19 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade nsupdate.info

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade nsupdate.info

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-2019-25091?

nsupdate.info: upgrade to 2019-05-19. Exact commands for each OS are on this page.

Is CVE-2019-25091 being exploited?

CVE-2019-25091 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-2019-25091 affect?

CVE-2019-25091 affects nsupdate.info. Severity is low (CVSS 3.7). A vulnerability classified as problematic has been found in nsupdate.info. This affects an unknown part of the file src/nsupdate/settings/base.py of the component CSRF Cookie Handler. The manipulation of the argument CSRF_COOKIE_HTTPONLY le

How urgent is CVE-2019-25091?

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

References

← Back to latest CVEs