All versions since 1.9.0
1.9.0
Upgrading
After upgrading an existing installation, run cxg pentest install --force. The
embedded Python pentest pipeline changes in this release, and replacing the binary alone
does not replace the files under ~/.cert-x-gen/pentest/.
Session liveness is now an authenticated API check, not a landing page. Capture,
cxg pentest auth verify, scan pre-flight and runtime health all call one API endpoint
on each profile’s own service. It defaults to /api/me and expects a 2xx; 401 and 403
always mean dead. If your application has no /api/me, its sessions now read as
unverified: configure a real authenticated endpoint with --me-path, or per profile
with auth import --liveness-path. --skip-health-check now skips only periodic
health checks and re-authentication. It no longer bypasses the startup API check. See
API session liveness and multiple services.
Request paths resolve at the service origin. fetch, fetchAs, raw, rawAs and
cxg.url no longer inherit a path from a landing --target such as
https://app.example/dashboard. The landing URL is still used for browser navigation.
Templates that relied on the implicit prefix must name their API prefix explicitly.
Report consumers:
report.jsonand the audit footer carryprofile_liveness(profile, service, origin, alive, status code, reason) andserviceswithready/unavailablestatus.- Exit 5 means a selected profile or service is unavailable or unverified. Probes for ready services still run, but the report is
complete: false,status: incomplete. - Scope and transport failures are recorded in
request_failuresand make the run incomplete with exit 4, even when a probe returns no findings.
Added
-
Engine-owned excluded-records oracle (
cxg.oracle.excludedRecords). It can refute a correct row-filtering fix. Such a fix keeps answering 200, so the refusal-control rule had nothing to observe and the fixed state stayed inconclusive. The engine issues three read-only GETs, each with its identity’s own credentials: the subject list as the attacker, the attacker’s own scoped list, and a reference list as a different identity. It compares records by key:- confirmed when a subject record outside the attacker’s list carries a reference value;
- refuted (proven) when the subject is non-empty and wholly inside the attacker’s list, the reference is non-empty, and both sessions were proven alive in the same run;
- inconclusive otherwise, naming the cause.
The verdict binds to the finding’s endpoint and applies only to cross-identity classes. It never overturns a proven confirmation and cannot be forged from template evidence. Generation prompt v8 documents it.
-
Per-profile service and liveness settings on
cxg pentest auth import:--service,--liveness-pathand repeatable--liveness-status. Captures and imports save them asliveness_check: {path, expected_status}, and existingliveness_pathmetadata still loads. -
Multi-service runs. Each profile opens its own service. Cross-origin
cxg.fetchAsuses that identity’s API request context, so a second service no longer fails on CORS. Scope, budgets, redirects and audit still apply at every hop.
Changed
- A denial verdict needs proof that both sessions were alive. Attacker and control liveness must come from the same run and service. Otherwise the result is
inconclusive_refusal, naming the unverified profiles. An expired session can no longer be recorded as a verified mitigation. - One unavailable profile no longer cancels the run. Profiles keep their roster indices, only the probes that need an unavailable profile are skipped, and other services continue.
- When an oracle observation cannot bind to a finding, triage names the measured request and the claimed endpoint. It no longer reports that the oracle saw no signal.
Fixed
- Oracle proofs bind to findings on dynamic paths such as
GET /users/{username}. Every SQLi and class-oracle router keeps the original request URL beside the substituted one. Binding accepts{param},:param,<param>and<type:param>, but a parameter never spans more than one segment. Method, origin, query and sibling-uniqueness checks are unchanged. - A public landing page can no longer make an expired bearer session look alive. Redirects, HTML fallbacks and missing endpoints do not count as liveness.
- The HTTP/2 race transport keeps reading responses already queued by a closing peer when an acknowledgment write fails. Previously those responses could be lost as all-zero statuses.
1.9.1
Upgrading
After upgrading an existing installation, run cxg pentest install --force. The fix
below is in the embedded Python pentest pipeline, and replacing the binary alone does not
replace the files under ~/.cert-x-gen/pentest/.
Fixed
cxg.oracle.excludedRecordsverdicts bind when the scope has a path. With a landing scope such as--scope http://host/dashboard, the oracle measured/api/xat the service origin while the finding claimed/dashboard/api/x, so a correct row-filtering fix came backinconclusive_refusal(unverified) instead of refuted (proven), and a leak was not confirmed by the oracle. The claim is now resolved at the service origin, the way the oracle’s requests are, through bothcxg scanandcxg pentest run. The other class oracles build their requests from the full--target, so their claims already bound and are unchanged.cxg pentest run --helpdescribed 1.8.0 session behaviour. It said a dead session only warns without--ciand that--skip-health-checkforce-marks profiles alive. Since 1.9.0 an expired profile exits 5 with or without either flag, and probes for ready services still run. The--ci,--skip-health-checkand exit-code 5 help now say so, and--cireads as what it still does: refuse a world-accessible--auth-dir.
[1.9.2] Latest
Upgrading
After upgrading an existing installation, run cxg pentest install --force. These fixes
are in the embedded Python pentest pipeline. cxg scan refreshes it on first use.
Fixed
- A profile is no longer unverified, and the run no longer exits 5, because the app has no
JSON
/api/me. When no liveness endpoint is configured and/api/meanswers 404, HTML, a redirect or nothing, the 1.8.0 landing test decides; a configured endpoint, or an/api/meanswering 401/403, still decides as in 1.9.x. Remaining 1.8.0 hole: an app with no API liveness endpoint, a public landing page and an expired bearer reads as alive. - A supplied-probe replay drops
--authnames with no loadable profile, as 1.8.0 did, so one missing profile no longer makes every kit, including anonymous ones, exit 5. - Identity traffic and liveness go to the
--scopetarget again. A profile’s saved--targetorigin is used only for a profile imported with--service; 1.9.x sent a stale profile’s requests to another port while the verdict was recorded against the scope. - Request helpers keep the
--scopepath prefix again, socxg.fetch/raw/urlandcxg.page.probeXssagree under a scope such ashttp://host/app/and an XSS that 1.8.0 confirmed confirms.cxg.oracle.excludedRecordsstill resolves at the origin. - A complete run reports
status: "ok", not"complete", so a consumer that treats any status other thanokas a caveat no longer reports one;incompleteis unchanged. - A blocked or failed request no longer changes the exit code to 4. It is still recorded
in
request_failuresand makes the runstatus: incomplete.

