dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-10548

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security flaw has been discovered in NousResearch hermes-agent up to 2026.4.23. This affects the function _sync_anthropic_entry_from_credentials_file of the file agent/credential_pool.py of the component Credential Pool Synchronization. The manipulation results in improper authentication. The attack must be initiated from a local position. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A local authentication bypass vulnerability exists in the hermes-agent credential pool synchronization. The _sync_anthropic_entry_from_credentials_file function in agent/credential_pool.py fails to properly validate authentication when processing credentials from a file, allowing a local attacker to manipulate credentials and gain improper authentication access.

MitigationRestrict file permissions on the credentials file to prevent tampering, implement cryptographic verification of credential integrity before synchronization, and validate all credential entries during the sync process.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the vulnerable function in source code
    Search for the file agent/credential_pool.py in your codebase and verify the existence of the _sync_anthropic_entry_from_credentials_file function. Use: find . -name 'credential_pool.py' -path '*/agent/*' and inspect the function definition.
    Affected if The function exists and handles credential synchronization from a credentials file
  2. Check if Anthropic credentials sync is enabled
    Examine your application configuration or runtime settings to determine whether the credential pool is configured to sync Anthropic credentials from a file. Look for config flags like 'sync_credentials', 'anthropic_credentials_file', or similar settings.
    Affected if Credential synchronization from file is enabled in the application configuration
  3. Inspect credentials file permissions
    Locate the credentials file being used (commonly ~/.anthropic/credentials, ~/.config/anthropic/credentials, or a custom path) and check its file permissions using: ls -la <credentials_file_path>
    Affected if The credentials file is readable by users other than the owner, or writable by other users
  4. Verify authentication validation in the function
    Review the _sync_anthropic_entry_from_credentials_file function code to check if it contains proper credential validation, user identity verification, or permission checks before processing credentials. Look for missing validation logic.
    Affected if The function lacks proper credential validation, access rights checks, or user identity verification before processing credentials
  5. Check application version against available patches
    Query your installed package or application version: pip show <package_name> or check git history for version tags. Compare against any published fixed versions.
    Affected if You cannot confirm the installed version includes a fix for this authentication bypass

You are affected if the _sync_anthropic_entry_from_credentials_file function exists in your environment and credential file synchronization is enabled, especially if the function lacks proper credential validation and the credentials file has overly permissive access rights.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict file permissions on the credentials file to prevent tampering, implement cryptographic verification of credential integrity before synchronization, and validate all credential entries during the sync process.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10548 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10548 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data