CVE-2026-22798: hermes is an implementation of the HERMES workflow to automatize software publication with rich metadata

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

hermes: upgrade to 0.9.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-22798 being exploited?

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

CVE-2026-22798 affects hermes. Severity is medium (CVSS 5.9). hermes is an implementation of the HERMES workflow to automatize software publication with rich metadata. From 0.8.1 to before 0.9.1, hermes subcommands take arbitrary options under the -O argument. These have been logged in raw form. If us

Q: How urgent is CVE-2026-22798?

Priority 22/100. No elevated risk signals yet.

Routine

MEDIUM 5.9UPGRADE

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

hermes is an implementation of the HERMES workflow to automatize software publication with rich metadata. From 0.8.1 to before 0.9.1, hermes subcommands take arbitrary options under the -O argument. These have been logged in raw form. If users provide sensitive data such as API tokens (e.g., via hermes deposit -O invenio_rdm.auth_token SECRET), these are written to the log file in plain text, making them available to whoever can access the log fi

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.2% (top 93%)
CISA exploited list	No
Weakness	CWE-532
Published	2026-01-12
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: software-metadata.pub

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

Am I affected?

Timeline

2026-01-12 22:16 UTCPublished CVE record published
2026-06-17 10:20 UTCUpdated Record last modified

software-metadata.pub hermes UPGRADE

Affected: >= 0.8.1 and < 0.9.1

Fixed in: 0.9.1

Safe to downgrade to: a release before 0.8.1

1. Check installed version

pip show hermes

2. UPGRADE to 0.9.1

pip install --upgrade "hermes>=0.9.1"

3. If no update is available yet, DOWNGRADE to a release before 0.8.1

pip index versions hermes pip install "hermes<0.8.1"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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

hermes: upgrade to 0.9.1. Exact commands for each OS are on this page.

Is CVE-2026-22798 being exploited?

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

CVE-2026-22798 affects hermes. Severity is medium (CVSS 5.9). hermes is an implementation of the HERMES workflow to automatize software publication with rich metadata. From 0.8.1 to before 0.9.1, hermes subcommands take arbitrary options under the -O argument. These have been logged in raw form. If us

How urgent is CVE-2026-22798?

Priority 22/100. No elevated risk signals yet.

Related CVEs

CVE-2025-1293 HIGH 8.2 UPGRADE Hermes versions up to 0.4.0 improperly validated the JWT provided when using the AWS ALB authentication mode,

References

← Back to latest CVEs