{"answers":{"affected":"3 open source packages ship an affected version, including hermes. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-22798 in the wild and no public exploit code.","fix":"Upgrade hermes to 0.9.1 or later.","what":"CVE-2026-22798 is a medium-severity vulnerability in softwarepub hermes, published on 12 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-22798 and fix it if it is affected.\n\nWhat it is: CVE-2026-22798 is a medium-severity vulnerability in softwarepub hermes, published on 12 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-22798 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- hermes (PyPI): affected from 0.8.1; fixed in 0.9.1\n- hermes (PyPI): affected from 0.8.1; fixed in 0.9.1\n- hermes (PyPI): affected from 0.8.1; fixed in 0.9.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-22798/ (Markdown: https://insights.sbomify.com/CVE-2026-22798/index.md)","id":"CVE-2026-22798","markdown":"https://insights.sbomify.com/CVE-2026-22798/index.md","name":"CVE-2026-22798","record":{"aliases":["GHSA-jm5j-jfrm-hm23","PYSEC-2026-1449"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python publication automation","requires_auth":"low_privilege","summary":"Attackers with log file access can read sensitive API tokens and secrets logged in plain text by the hermes tool.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"hermes","vendor":"software-metadata.pub"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"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 file. This vulnerability is fixed in 0.9.1.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"hermes's raw options logging may disclose secrets passed in via subcommand options argument","id":"CVE-2026-22798","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"emlog Arbitrary File Upload Vulnerability","id":"CVE-2026-22799"},"packages":[{"ecosystem":"PyPI","fixed":["0.9.1"],"introduced":["0.8.1"],"last_affected":[],"package":"hermes","purl":null,"source":"GHSA-jm5j-jfrm-hm23"},{"ecosystem":"PyPI","fixed":["0.9.1"],"introduced":["0.8.1"],"last_affected":[],"package":"hermes","purl":"pkg:pypi/hermes","source":"GHSA-jm5j-jfrm-hm23"},{"ecosystem":"PyPI","fixed":["0.9.1"],"introduced":["0.8.1"],"last_affected":[],"package":"hermes","purl":"pkg:pypi/hermes","source":"PYSEC-2026-1449"}],"prev":{"headline":"Auth bypass in keystonemiddleware","id":"CVE-2026-22797"},"products":["hermes"],"published":"2026-01-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-13","vendors":["softwarepub"]},"summary":"Attackers with log file access can read sensitive API tokens and secrets logged in plain text by the hermes tool.","url":"https://insights.sbomify.com/CVE-2026-22798/"}