Skip to content
Reachability Analysis

Agent investigation is only as checkable as the evidence record it leaves behind

A record has seven parts, and each part fails in its own way

A conclusion alone is a claim. A record someone else can replay holds the parts below. The agent or the platform writes parts one to six, and a named person writes the seventh.

The four-question tool on the home page sends a finding to agent investigation when a control sits in front of the service, or when two or three of code called, service reached and control in front are not sure. Those are the findings whose answer sits in configuration, logs and files, which is what this record holds.

PartWritten byUsual failure
1. Finding and assetPlatform, from the scannerAsset identity is a name that was reused
2. Access heldPlatform, from the grantLists the role requested, not the access in force
3. Sources read, with timeAgentGives no time, so a stale read looks current
4. Tests against advisory preconditionsAgentCites no advisory text, or tests a different condition
5. Conclusion and scopeAgentSays 'not exploitable' with no asset and date
6. Unknowns, with the reasonAgentOmitted, so a gap reads as a pass
7. Review and expiryHuman reviewerMissing, so the closure never expires

A complete sample record for CVE-2026-82329 on one Artifactory instance

The question here is not only 'is the version affected' but 'was this instance compromised', which is why CVE-2026-82329 suits agent investigation. Fastly reports disclosure on 28 Aug 2026, about 171,000 attempts on 1 Sep 2026 and a peak near 406,000 on 2 Sep 2026. The instance, hosts, dates and counts in the record are an illustration. The advisory facts are real.

Parts one and two come first.

FieldEntry
RecordINV-4417, version 1, opened 19 Nov 2026 09:12 UTC
FindingCVE-2026-82329, JFrog Artifactory Access service join-key authentication bypass, CVSS 9.8, added to KEV on 2 Sep 2026, first mass exploitation 1 Sep 2026 (Fastly)
Assetartifactory-prod-1, self-hosted, owner Platform Engineering
Access heldRead-only API token with scope for system version and user listing; read-only search on the reverse-proxy log index. It holds no shell, file-system or write access
Access granted byPlatform Engineering lead, 3 Nov 2026, expires 3 Feb 2027

The sample record's tests each name a precondition, a source and a time

The advisory preconditions are a self-hosted release in an affected range, a default install with no additionalJoinKeys set, and network access to the join endpoint. On a default install the Access service trusts an empty join key. The attack, as Fastly describes it, is a request to POST /access/api/v1/registry/join carrying a forged token whose key ID is the SHA-256 of the empty string, e3b0c442...b855. Fastly calls an HTTP 201 tied to that key ID "high-confidence evidence of compromise".

Scroll the table sideways for more columns

TestSource, time (UTC)ObservedResult
T1 Release affected nowGET system version, 19 Nov 2026 09:147.146.38Fixed build. JFrog's table lists 7.146.0 to 7.146.36 as affected and NVD treats every release below 7.146.38 as affected. 7.146.37 is in neither JFrog's affected list nor its patched list, so only 7.146.38 counts as fixed
T2 Release affected during exposureChange ticket CHG-9120, read 09:15Upgrade from 7.146.30 to 7.146.38 closed 9 Sep 2026Affected from 28 Aug to 9 Sep 2026 (12 days); 7.146.30 is inside both JFrog's and NVD's range
T3 Join endpoint reachableReverse-proxy routing config as exposed in the log index, 09:17Route to /access/ open to the corporate VPN range onlyNot internet reachable; reachable from the VPN range
T4 Join requests with an HTTP 201Log index search, join path, status 201, 09:21Retention starts 21 Sep 2026. 0 matching requests from 21 Sep to 19 Nov 2026No evidence of compromise in the retained window
T5 Unexpected admin usersUser listing, 09:244 admins, all on the owner's rosterNo unexpected admin
T6 Groovy user pluginsNeeds file-system accessNot runUnknown
T7 Join key rotated and tokens revoked since 28 Aug 2026Change tickets, search 'join key', 09:27No ticket foundNot done on record

The sample record's conclusion states its scope and lists its unknowns

  • Conclusion: artifactory-prod-1 is not vulnerable on its current release (T1). It was on an affected release from 28 Aug to 9 Sep 2026 (T2) and was reachable only from the VPN range (T3), so exposure to internet scanning was limited.
  • Compromise: unknown for 28 Aug to 20 Sep 2026, because the log index starts on 21 Sep 2026 (T4). No sign of compromise from 21 Sep 2026 onward (T4, T5).
  • Unknown, plugins: the agent holds no file-system access, so T6 was not run.
  • Open action for the reviewer: the ledger mitigation says patching does not revoke tokens already issued and advises rotating the platform join key and revoking tokens issued since 28 Aug 2026. T7 found no record that either was done.
  • Status: needs human action, not closed. Reviewer: Platform Engineering lead. Expiry of any later closure: 19 Feb 2027, or on a new advisory revision.
  • Version history: v1 only. A later version adds a row below with its date and the evidence that changed.

A reviewer replays a record in five steps

The same five steps work on any vendor's record. Run them on a record for a finding you already understand, and include one you expect to come back unknown.

  • Open the advisory and confirm the record quotes a precondition from it, not a paraphrase of the title.
  • For each test, repeat the source read yourself, or confirm the source and time are specific enough that you could.
  • Check the access list against the sources: every source read must fall inside the access held. T6 above shows a source outside it, correctly marked unknown.
  • Look for the unknowns. A record with no unknown on a finding whose evidence needs logs, files or hosts the agent cannot read has hidden a gap.
  • Confirm a person is named for the closure and that an expiry or trigger is set. The agent reads, and people decide on closures that become exceptions.

Four vendors describe how their products show evidence

These are the vendors' own statements, in alphabetical order. They describe design, not measured accuracy, and none comes with a sample record.

  • Cogent: "Every output includes the full chain of logic: data sources queried, agents involved, and why this path was selected over alternatives." When signal is short it says it "will surface unknowns/low confidence".
  • Maze: "Every recommendation comes with the evidence and reasoning behind it."
  • Onit: a Reachability Agent marks each exposure Reachable, Not Reachable or Unknown, and "when evidence is missing, an agent returns 'unknown' with the reason".
  • Seemplicity: AI Analysts investigate each asset by analyzing "live runtime configurations, exploit prerequisites, network reachability, code and dependency usage, and compensating controls".

Sampling closures measures your own deployment

Pull ten findings closed as not exploitable each month, read each record with the five steps above and count how many the reviewer reopens. That count is specific to your deployment. Keep the agent's access list under change control too, since a record that cites a source the agent can no longer reach cannot be replayed.

Sources

  1. Fastly on CVE-2026-82329, 3 Sep 2026, read 19 Nov 2026
  2. Cogent AI engine page, read 19 Nov 2026
  3. Maze cloud platform page, read 19 Nov 2026
  4. Onit blog on AI agents in vulnerability management, read 19 Nov 2026
  5. Seemplicity AI Analysts announcement, read 19 Nov 2026
  6. JFrog security advisories (CVE-2026-82329 affected and patched versions), read 19 Nov 2026
  7. NVD record for CVE-2026-82329, read 19 Nov 2026
  8. CISA KEV entry for CVE-2026-82329 (added 2 Sep 2026), read 19 Nov 2026

Last reviewed 19 Nov 2026.