dbcve.org
Ssh AgentApplication · Jenkins

CVE-2025-32754

CRITICAL · 9.1 CVSS v3.1 Published 2025-04-10
Fix available
A fix is available. Upgrade to 6.11.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
In jenkins/ssh-agent Docker images 6.11.1 and earlier, SSH host keys are generated on image creation for images based on Debian, causing all containers based on images of the same version use the same SSH host keys, allowing attackers able to insert themselves into the network path between the SSH client (typically the Jenkins controller) and SSH build agent to impersonate the latter.

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 · high confidence

The jenkins/ssh-agent Docker images (6.11.1 and earlier) based on Debian generate SSH host keys during image build time rather than container runtime. This causes all containers instantiated from the same image version to share identical SSH host keys, enabling man-in-the-middle attackers who can intercept network traffic between the Jenkins controller and SSH build agent to impersonate the agent.

MitigationRegenerate unique SSH host keys at container runtime by modifying the Docker image entrypoint to generate fresh keys on each container start, rather than at image build time. Existing deployments should be rotated.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ssh AgentApplication
Affected:< 6.11.2

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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. Identify the installed jenkins/ssh-agent image version
    Run 'docker images' or 'docker inspect <container>' to retrieve the image tag. Check if the version tag is earlier than 6.11.2.
    Affected if The image version shown is 6.11.1 or earlier.
  2. Inspect SSH host keys present in the image
    Extract or inspect the Docker image filesystem and look for SSH host keys in /etc/ssh/ (such as ssh_host_rsa_key, ssh_host_ecdsa_key, or ssh_host_ed25519_key).
    Affected if SSH host key files exist in /etc/ssh/ within the image, indicating keys were generated at image build time.
  3. Verify host key persistence across container restarts
    Start a container from the image, note the SSH host key fingerprint (e.g., using 'ssh-keygen -lf /etc/ssh/ssh_host_rsa_key'), stop the container, then start a new container from the same image and compare the fingerprint.
    Affected if The host key fingerprints are identical between separate container instances, confirming keys are baked into the image rather than generated at runtime.

You are affected if you are using a jenkins/ssh-agent image version earlier than 6.11.2 and the SSH host keys are identical across different container instances, indicating they were generated during image build rather than at container startup.

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.

dbcve · scoped
Upgrade available Upgrade to 6.11.2 or later
Fixed in 6.11.2
Interim mitigation

Regenerate unique SSH host keys at container runtime by modifying the Docker image entrypoint to generate fresh keys on each container start, rather than at image build time. Existing deployments should be rotated.

Recommended fix High confidence

jenkins/ssh-agent:6.11.2 or later

  1. Pull the fixed Docker image: docker pull jenkins/ssh-agent:6.11.2 (or latest stable version)
  2. Update your deployment configuration, Kubernetes manifests, Docker Compose files, or Jenkins pipeline configurations to reference the new image version
  3. Rebuild and redeploy all containers running the vulnerable ssh-agent image
  4. Verify that SSH host keys are regenerated on each container start rather than being static across containers (you can check /etc/ssh/ssh_host_* keys inside the container)
  5. Restart any SSH connections to agents to ensure they use the new unique host keys

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ssh Agent Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32754 — 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-2025-32754 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