CVE-2026-71881: Multiple injection issues in resource metadata fields in GBIF Integrated Publishing Toolkit versions before 3.

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

integrated publishing toolkit: upgrade to 3.3.5. Exact commands for each OS are on this page.

Q: Is CVE-2026-71881 being exploited?

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

CVE-2026-71881 affects integrated publishing toolkit. Severity is medium (CVSS 4.8). Multiple injection issues in resource metadata fields in GBIF Integrated Publishing Toolkit versions before 3.3.5 allows authenticated remote attackers to execute code in another user's session after user interaction via stored cross-site s

Q: How urgent is CVE-2026-71881?

Priority 17/100. No elevated risk signals yet.

Routine

MEDIUM 4.8UPGRADE

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

Multiple injection issues in resource metadata fields in GBIF Integrated Publishing Toolkit versions before 3.3.5 allows authenticated remote attackers to execute code in another user's session after user interaction via stored cross-site scripting

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.8 (Medium)
EPSS exploit chance	n/a
CISA exploited list	No
Weakness	CWE-79
Published	2026-11-06
Last modified	2026-11-06

Publisher (CNA): Mandiant · Vendor: gbif · Source: CVE Program record (NVD analysis pending)

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

Am I affected?

Timeline

2026-11-06 23:29 UTCPublished CVE record published
2026-11-06 23:29 UTCUpdated Record last modified

gbif integrated publishing toolkit UPGRADE

Affected: < 3.3.5

Fixed in: 3.3.5

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy integrated-publishing-toolkit || rpm -q integrated-publishing-toolkit || integrated-publishing-toolkit --version

2. UPGRADE to 3.3.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade integrated-publishing-toolkit

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade integrated-publishing-toolkit

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

integrated publishing toolkit: upgrade to 3.3.5. Exact commands for each OS are on this page.

Is CVE-2026-71881 being exploited?

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

CVE-2026-71881 affects integrated publishing toolkit. Severity is medium (CVSS 4.8). Multiple injection issues in resource metadata fields in GBIF Integrated Publishing Toolkit versions before 3.3.5 allows authenticated remote attackers to execute code in another user's session after user interaction via stored cross-site s

How urgent is CVE-2026-71881?

Priority 17/100. No elevated risk signals yet.

References

← Back to latest CVEs