# kr2s-was-i-vulnerable

Checks whether a Rails app was ever exposed to CVE-2026-66066 in production, and if so gives the exposure window.

Skill by Ruby on Rails. Category: Security.

## Install

Project (for this project only):

```sh
npx skills add rails/rails-forensics-cve-2026-66066 --skill kr2s-was-i-vulnerable
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

Global (for every project on this machine):

```sh
npx skills add rails/rails-forensics-cve-2026-66066 --skill kr2s-was-i-vulnerable -g
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

## Tags

- Runs on your computer: It runs as a program on your machine, with your access.

## Security audits

- Gen Agent Trust Hub: Pass
- Socket: Pass
- Snyk: Pass

Installs: 2. Installs counted by skills.sh. [Open on skills.sh](https://www.skills.sh/rails/rails-forensics-cve-2026-66066/kr2s-was-i-vulnerable)

## Source

[Open the source](https://github.com/rails/rails-forensics-cve-2026-66066/tree/HEAD/skills/kr2s-was-i-vulnerable). Checked 2026-10-10. This summary may contain AI-generated text, so it can be wrong. Check the source before you rely on it.

## SKILL.md

````markdown
---
name: kr2s-was-i-vulnerable
description: |
  Determine whether a Rails application was ever exposed to CVE-2026-66066, and
  if so produce the exposure window and the other facts a forensic sweep needs.
  Runs first; kr2s-was-i-exploited consumes its output.
triggers:
  - kr2s-was-i-vulnerable
  - was i vulnerable
  - were we vulnerable
  - am i vulnerable
  - are we affected by CVE-2026-66066
  - CVE-2026-66066
  - GHSA-xr9x-r78c-5hrm
  - KindaRails2Shell
  - is this app affected by the libvips rails vulnerability
  - active storage libvips vulnerability
  - matload vulnerability rails
  - do we use vips variant processor
  - exposure window for CVE-2026-66066
  - when were we vulnerable
---

# kr2s-was-i-vulnerable

Open `@references/guide.md` and follow it. Do not proceed without it.

Determines whether a Rails application was ever exposed to CVE-2026-66066
(GHSA-xr9x-r78c-5hrm), and produces the facts that `kr2s-was-i-exploited`
requires before it can sweep anything.

**The deliverable is a window, not a yes or no.** For most applications reading
this today the present-tense answer is "no, we patched." The useful answer is
the period during which the vulnerable code was serving production traffic,
because that is what bounds the search for evidence.

Two things follow, and both are easy to get wrong.

The vulnerable code is gone from `HEAD`. Analyzing the current tree proves
nothing. You have to check out the tree as it stood before the fix.

The window is bounded by deploy dates, not commit dates. Using the commit date
for the end of the window closes it before the fix was actually running, and
silently drops any attack in the gap.
````

- Previous: [kr2s-was-i-exploited](https://syn4pse.dev/terminal/rails-kr2s-was-i-exploited.md)
- Next: [ai-infra](https://syn4pse.dev/terminal/ai-infra.md)
- [Terminal](https://syn4pse.dev/terminal.md)
- [Suggest a change](mailto:terminal@syn4pse.dev?subject=Terminal%20suggestion)
