dbcve.org
Insight AgentApplication · Rapid7

CVE-2026-4482

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-10
Fix available
A fix is available. Upgrade to 4.1.0.2 or later.
See remediation →
57/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
The installer certificate files in the …/bootstrap/common/ssl folder do not seem to have restricted permissions on Windows systems (users have read and execute access). For the client.key file in particular, this could potentially lead to exploits, as this exposes agent identity material to any locally authenticated standard user.

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

The client.key file and other SSL certificate files in the bootstrap/common/ssl folder have overly permissive Windows file permissions, allowing any locally authenticated standard user to read the private key material. This exposes agent identity credentials, potentially enabling privilege escalation or impersonation attacks.

MitigationRestrict file permissions on the SSL folder and its contents (especially client.key) to require Administrator or SYSTEM-level access, removing read access for standard users.

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
Insight AgentApplication
Affected:< 4.1.0.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Insight Agent installation path
    Locate the Rapid7 Insight Agent installation directory, typically found in C:\Program Files\Rapid7\Insight Agent or C:\Program Files (x86)\Rapid7\Insight Agent. Check the version by right-clicking the agent executable or checking the product version in Windows Programs and Features.
    Affected if The installed version is lower than 4.1.0.2
  2. Locate the SSL certificate folder
    Navigate to the bootstrap\common\ssl subfolder within the Insight Agent installation directory. Confirm the presence of certificate files, particularly client.key.
    Affected if The folder bootstrap\common\ssl exists and contains SSL certificate files including client.key
  3. Verify file permissions on client.key
    Right-click client.key, select Properties, then go to the Security tab. Click on Users or the relevant standard user group and check the Allow permissions under the Read column.
    Affected if Standard users (non-Administrators) have Read permission granted on client.key
  4. Check permissions on other SSL files
    In the same bootstrap\common\ssl folder, inspect permissions on all certificate files (.key, .pem, .crt, .pfx). Review each file's Security tab to confirm if standard users have Read access.
    Affected if Any SSL certificate files in this folder are readable by standard users

If the Insight Agent version is below 4.1.0.2 AND the SSL certificate files in the bootstrap\common\ssl folder are readable by standard users, the environment is vulnerable to credential exposure via CVE-2026-4482.

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 4.1.0.2 or later
Fixed in 4.1.0.2
Interim mitigation

Restrict file permissions on the SSL folder and its contents (especially client.key) to require Administrator or SYSTEM-level access, removing read access for standard users.

Recommended fix Moderate confidence

Insight Agent 4.1.0.2 or later

  1. 1. Download Insight Agent version 4.1.0.2 or later from the official Rapid7 source
  2. 2. Back up the current Insight Agent installation and configuration
  3. 3. Uninstall the current (vulnerable) Insight Agent version
  4. 4. Install the new Insight Agent version 4.1.0.2 or later
  5. 5. After installation, verify that certificate files in the ../bootstrap/common/ssl folder (especially client.key) have restricted permissions - only SYSTEM and Administrators should have read/write access, standard users should have no access
Caveat Standard upgrade best practices apply - test in non-production environment first

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

Fix this in Insight Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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