PAGES
Subscribe Get it delivered — five to ten releases we picked each morning from the tools you run, with every release in the issue on the web. Compare plans →

The Cyber Toolchain — issue 047, August 16, 2026

THE CYBER TOOLCHAIN NO. 047
Tail
THE DAILY RELEASE FIREHOSE
PUBLISHED AUGUST 16, 2026 · EVERY DAY
EDITIONS tail grep head ls diff uniq

The daily firehose — everything the toolchain shipped today, already filtered.

We read every release from the 1309 tools on our watchlist at the source — GitHub and GitLab release notes, vendor release pages and changelogs, project blogs and feeds, vendor press releases, and the source code behind the tag. Bug-fix-only releases and non-product newsroom noise are dropped; what's left is summarized down to the new capability, how to try it, and any screenshots or videos the release itself published. Every entry links to the sources it was built from.

VIEW
ISSUE VIEW scroll
ISSUE WIDTH reading width
Do you prefer scroll?
ADDITIONAL FILTERS
$ tct list   # 14 tools matched
Application Security
◆  Secrets Detection & Management

GitGuardian SaaS

Sources Changelog → 1 release · 2026-08-16 Changelog

GitGuardian SaaS is a cloud-based security platform that detects and prevents secret leaks in Git repositories and source code.

GitGuardian SaaS added new API endpoints for secret location listing and live scan progress, plus a custom secret-validity API, honeytoken protection for developer endpoints, and programmatic PATPATA personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it./SAT token management.

└──▷ WHAT SHIPPED · 5 FEATURES 2 OF 5 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Secret location listing by incident and source new 95

New GET /v1/incidents/secrets/{incident_id}/locations endpoint lists every file on a source's default branch still holding a secret for a given incident, with exact line positions, filterable by source, number_of_mentions_min, number_of_mentions_max, code_fix_request_status (processing, created, error), and search (filepath substring), sortable by last_updated_at, number_of_mentions, or source. A companion GET /v1/sources/{source_id}/locations endpoint lists all files in a single source with any secret on the default branch, carrying the same per-match line positions, filters, and sort options.

Find every file still exposing the secret for a given incident, scoped to actively monitored sources with more than one mention, to prioritize remediation.
$ curl -s -H 'Authorization: Token <api_key>' 'https://api.gitguardian.com/v1/incidents/secrets/42/locations?monitored=true&number_of_mentions_min=2&ordering=-number_of_mentions'
List all secret locations in a specific source that match a filepath pattern, to hand off an exact file list to the owning team.
$ curl -s -H 'Authorization: Token <api_key>' 'https://api.gitguardian.com/v1/sources/5523/locations?search=settings.py&code_fix_request_status=created'
— Full endpoint paths, filters, and runnable curl examples given. api-docs-983de2edf972
02 01
Honeytoken protection for developer endpoints new 93

The ggshield honeytoken plant command (via the existing agent binary) plants a decoy AWS credential on developer endpoints; any use of the decoy triggers an alert naming the compromised machine, its IP address, user agent, and timestamp, with no new agent required. A new Honeytoken protection card in the Endpoints dashboard reports fleet coverage percentage and lists unprotected endpoints.

Plant a honeytoken on a developer machine to detect credential-harvesting malware the moment it reads the credential file.
$ ggshield honeytoken plant
— Named command, alert fields, and dashboard card, with runnable example. changelog-20260816-37c07038
03 00
Live scan progress polling endpoint new 90

New beta GET /v1/scans/{scan_id}/live-progress endpoint returns the live status (queued, in_progress, completed) and real-time counters (elements_scanned, elements_total, elements_skipped, elements_failed, data_downloaded_bytes, data_scanned_bytes) for a running historical scan, including an audit_url field once the scan completes.

Poll a running historical scan for live progress counters and stop when completed is returned, then fetch the audit summary from audit_url.
$ curl -s -H 'Authorization: Token <api_key>' 'https://api.gitguardian.com/v1/scans/<scan_id>/live-progress'
— Named endpoint and fields with a runnable poll example. api-docs-983de2edf972
04 02
Custom secret validity submission via API new 70

A new API endpoint lets teams push their own validity status (valid or invalid) for secrets on unreachable internal systems, authenticated with a personal access tokenpersonal access tokenA personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. scoped to secrets:write; the status propagates to all incidents for that secret, appears as Custom validity with a datestamp, and is recorded in the incident activity log and audit log.

— Scope and effects named but exact endpoint path missing. changelog-20260816-37c07038
05 00
Programmatic PAT/SAT creation and audit logging new 60

The API now supports creating Personal Access Tokens (PATsPATsA personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it.) and Service Account Tokens (SATs) programmatically for automated token rotation workflows; tokens created via the API must have a finite TTLTTLTime to live, a limit on how long data remains valid or how far a packet can travel. Caches use a time limit; IP packets use a hop limit.. Scans triggered via a Personal Access Token now also emit an audit log event.

— Mechanism and TTL rule named but no endpoint path given. changelog-20260816-37c07038
└──▷ ALSO FROM THESE RELEASES
Was this useful?
Reverse Engineering, Malware & Forensics
◆  Malware Analysis

CAPEv2

Sources Commits → changes since 2026-08-14 Code

Malware Configuration And Payload Extraction

CAPEv2 adds advanced configuration options in this release.

  • Adds advanced configuration options to extend sandbox behavior (see PR #3160 for details).

1 detail in Everything

Was this useful?
Network Security
◆  IDS / IPS

Fail2ban

Sources Release notes →Source code → 1 release · 2026-08-15 Notes Code

Daemon to ban hosts that cause multiple authentication errors

Fail2ban 1.1.1 adds file-based IP allowlists with dynamic reload, a new OpenVPN jail and CSFCSFThe NIST Cybersecurity Framework, a set of outcomes for managing cybersecurity risk. Organizations use it to describe their current posture, priorities and improvement goals. firewall action, and extends the exim and sshd filters with new detection modes.

└──▷ WHAT SHIPPED · 8 FEATURES 0 OF 8 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
File-based IP allowlists via ignoreip new 95

Extends ignoreip with file:... (or file://path/file-with-ip-set) syntax to load ignored IPs, subnets, DNS/FQDN, or raw strings from an external file. The file is read lazily and reloaded dynamically when it changes, with comments after # or ; ignored; implemented via the new FileIPAddrSet class in ipdns.py.

Maintain a shared allowlist file of trusted IPs and subnets that Fail2ban reloads automatically — useful for dynamic allowlists shared across jails.
ini
# In jail.local or jail.conf
[DEFAULT]
ignoreip = 127.0.0.1/8 ::1 file:///etc/fail2ban/trusted-ips.txt
— Full mechanism, exact syntax and reload behaviour with runnable config 1.1.1
02 00
Extended filter modes for exim and sshd improved 80

Adds filter.d/exim.conf mode more (several rules split out from mode normal) and extends mode aggressive to catch ACLACLAn access control list, a set of rules allowing or denying operations for particular users, services or network addresses. It decides who can use a resource.-dropped failures such as ACL: Country is banned. Also extends filter.d/sshd.conf modes ddos and aggressive with regex for timeout-before-authentication connections.

Enable aggressive exim filtering to also block connections dropped by ACL rules (e.g. country bans) in addition to normal authentication failures.
ini
# In jail.local
[exim]
enabled = true
filter  = exim[mode=aggressive]
— Names exact filter files and modes with a config example 1.1.1
thinner coverage below
03 00
New OpenVPN jail and CSF firewall action new 45

Adds a new OpenVPN jail (filter.d/openvpn.conf) and a new CSF (ConfigServer Firewall) action, comparable to the existing APF action.

— Names new filter and action but no usage detail 1.1.1
04 00
systemd-journal support for vsftpd and lighttpd-auth filters new 45

Adds systemd-journal regex support to filter.d/vsftpd.conf and filter.d/lighttpd-auth.conf.

— Names both filter files, no further mechanism given 1.1.1
05 00
Observer module tracks manual ban attempts improved 35

Makes manually added ban attempts inform the observer module, taking the known ban-count of bad IPs into account.

— Explains behaviour but no config surface or example 1.1.1
06 00
Default mysql_log path updated improved 30

Updates paths-common.conf to change the default mysql_log path, which is the default logpath for the mysqld-auth jail.

— Names config file and jail but not the new path value 1.1.1
07 00
OpenRC init script starts after nftables improved 30

Updates the OpenRC init script (files/fail2ban-openrc.init.in) to start after nftables in addition to iptables.

— Names exact file and firewalls affected, minimal detail 1.1.1
08 00
Debian package enables systemd fail2ban.socket new 30

Debian package now installs and enables a systemd-managed fail2ban.socket (gh-4220).

— Names the socket unit and issue reference, no usage detail 1.1.1
Was this useful?
◆  Firewalls & Network Defense

Rspamd

Sources Release notes → 1 release · 2026-08-15 Notes

Rapid spam filtering system.

Rspamd 4.1.5 introduces fuzzy sender-fact sharing over encrypted fuzzy rules, font-aware PDF text extraction, and a restructured Elastic fuzzy-results schema, alongside a wave of breaking changes covering file/SHM input gating, the GPT condition callback, fuzzy storage ACLsACLsAn access control list, a set of rules allowing or denying operations for particular users, services or network addresses. It decides who can use a resource. and encryption enforcement, and new controller/proxy connection limits.

└──▷ WHAT SHIPPED · 10 FEATURES 4 OF 10 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 01
TCP gating for file and shared-memory message inputs breaking 96

allow_file_and_shm_inputs is added explicitly to the normal, controller, and proxy worker configs (local.d/worker-normal.inc, local.d/worker-controller.inc, local.d/worker-proxy.inc) to gate TCPTCPA network protocol that delivers a reliable, ordered stream of bytes between two endpoints. It detects lost data and retransmits it. access to File, Path, and Shm message inputs; unix-socket connections always retain the capability, and the option must not be exposed to untrusted networks. It defaults to true in 4.1.5 with a startup warning on every TCP listener, but will default to false in the next major release, so TCP clients supplying file paths or shared-memory inputs must migrate to a unix socket before then. The proxy also strips client-supplied Shm* headers and File, Path, Shm query arguments, so scanning local files through the proxy no longer works and such clients must connect directly to a scanner listener.

Explicitly opt in to file and shared-memory message inputs on TCP before the default changes to false in the next major release.
hcl
allow_file_and_shm_inputs = true;
Opt in to the future-default now to silence TCP startup warnings on workers that have no clients using file or SHM inputs.
ini
# local.d/worker-normal.inc
allow_file_and_shm_inputs = false;
— Exact config keys across three files with runnable examples and migration deadline. 4.1.5
02 00
Structured fuzzy match results in Elastic plugin breaking 90

The fuzzy_nested option in local.d/elastic.conf switches the fuzzy results field from a flat fuzzy_hashes list to the Elasticsearch nested type, with per-match objects from task:get_fuzzy_results() containing rule, symbol, found, queried hashes, type, probability/prob, flag, and exactness/exact; the schema also adds an explicit mapping for message size. Saved searches, dashboards, and ingest pipelines referencing the old flat field must be updated — indices created after the upgrade use the new mapping shape while pre-upgrade indices retain the old one.

Enable structured nested fuzzy match objects in Elasticsearch to get per-match rule, probability, flag, and hash fields instead of a flat list.
hcl
fuzzy_nested = true;
— Exact config key, field names and a runnable example given. 4.1.5
03 00
Fuzzy sender facts sharing over encrypted rules breaking 88

Rules sharing extensions with their storage now attach a sender-facts extension to fuzzy check commands sent over encrypted connections, carrying SPFSPFAn email authentication standard that lets a domain owner publish, via DNS, which mail servers are authorized to send on its behalf, so receiving servers can reject spoofed senders., DKIMDKIMAn email authentication standard that lets a sending mail server cryptographically sign outgoing messages so receiving servers can verify the signature was not forged or tampered with in transit., and DMARC results, PTR state (including generic/dynamic hostname verdict from hfilter), bucketed recipient count, and TLS usage; FUZZY_CALLBACK gains ordering dependencies so authentication results are available when commands are built. A new no_share = true per-rule flag in local.d/fuzzy_check.conf disables sender-facts sharing on specific fuzzy rules. Fuzzy storage nodes older than 4.1.5 cannot skip this new extension type and will reject the entire fuzzy command with no reply to scanners — all fuzzy storage nodes must be upgraded to 4.1.5 before scanners, or no_share = true set on affected rules.

Temporarily disable sender-facts extension sharing on a fuzzy rule whose storage cannot yet be upgraded to 4.1.5.
ini
# local.d/fuzzy_check.conf, inside the affected rule
no_share = true;
— Names extension fields, callback and config key, plus upgrade order requirement. 4.1.5
04 00
Controller and proxy worker connection and auth limits new 86

max_auth_failures and auth_failure_window in local.d/worker-controller.inc rate-limit failed controller password attempts per source (default: 10 failures in 60s triggers HTTP 429; set max_auth_failures = 0 to disable). max_connections and max_connections_per_source limits are also added to the controller and proxy workers.

Tune controller auth rate-limiting to allow more attempts before throttling, or disable it entirely for a trusted internal deployment.
ini
# local.d/worker-controller.inc
max_auth_failures = 20;
auth_failure_window = 120s;
— Exact config keys, defaults and a runnable tuning example. product docs
05 02
GPT module condition callback signature change breaking 75

The gpt module's condition callback in local.d/gpt.conf now returns only a boolean verdict plus an optional reason string, instead of both a decision and request content; request content generation moves internally into gpt_check. Deployments whose condition callback also returned content will have that content silently ignored and must update it to return the boolean decision alone.

— Names config file, callback and exact behavior change, no code sample. 4.1.5
06 03
encrypted_only no longer exempts local peers breaking 75

encrypted_only = true in local.d/worker-fuzzy.inc no longer exempts peers with local or link-local source addresses — all clients, including those on localhost, must now use encryption (encryption_key in their fuzzy_check rule) or encrypted_only must be removed.

— Exact config file, option and required remediation named. product docs
07 04
Per-key forbidden_ids no longer merges with worker list breaking 73

Per-key forbidden_ids ACLs in fuzzy storage no longer additively merge with the worker-level forbidden_ids option — keys that previously relied on the global list to suppress additional flags must have those flag IDs added explicitly to their own forbidden_ids list.

— Names the exact option and before/after behavior, no config path given. product docs
08 00
URL filtering and symbol firing fixes breaking 68

url:get_urls_filtered() called without an include list (used by rspamadm mime urls and the URI_COUNT_ODD rule) no longer drops flag-less URLs such as those extracted from HTML parts, correcting the parity check for multipart/alternative messages. As a result, HFILTER_HELO_IP_A and URI_COUNT_ODD now fire in cases where they previously did not — local score overrides and composites involving these symbols may produce different scores after upgrade.

— Names the function, command and two symbols affected by the fix. product docs
09 00
Font-aware PDF text extraction new 65

Adds font-aware PDF simple font text decoding to libmime, supporting the three Annex D base encodings and per-font /Differences overrides, with a builder producing a single UTF-8 buffer per page. Also adds PDF /ToUnicode CMap parsing for composite (Type0) fonts, supporting codespace ranges, bfchar, bfrange, and UTF-16BE destinations including surrogate pairs; the CMap takes precedence over /Encoding.

— Detailed mechanism but no user-facing config or flag to act on. 4.1.5
thinner coverage below
10 00
Scanner backpressure from in-flight TCP connections improved 43

The scanner's max_tasks counter now includes accepted TCP connections still transmitting their body, enabling earlier backpressure on saturated scanners.

— Describes the mechanism but has no config knob or number. product docs
└──▷ BREAKING ON UPGRADE
  • !
    The condition callback for the GPT plugin now returns only a boolean (plus an optional reason) instead of both a decision and request content; deployments whose condition returned request content must update it to return the boolean decision alone.
  • !
    The allow_file_and_shm_inputs default will become false in the next major release; operators relying on file or shared-memory inputs over TCP should set allow_file_and_shm_inputs = true explicitly now.
  • !
    Fuzzy storage nodes older than 4.1.5 cannot skip the new sender-facts extension type and will reject the entire fuzzy command, returning no reply to scanners — upgrade all fuzzy storage nodes to 4.1.5 before upgrading scanners, or set no_share = true on affected rules in local.d/fuzzy_check.conf.
  • !
    Per-key forbidden_ids ACLs in fuzzy storage no longer additively merge with the worker-level forbidden_ids option — keys that previously relied on the global list to suppress additional flags must have those flag IDs added explicitly to their own forbidden_ids list.
  • !
    encrypted_only = true in local.d/worker-fuzzy.inc no longer exempts peers with local or link-local source addresses — all clients, including those on localhost, must now use encryption (encryption_key in their fuzzy_check rule) or encrypted_only must be removed.
  • !
    The proxy now strips client-supplied Shm* headers and File, Path, Shm query arguments — scanning local files through the proxy no longer works; such clients must connect directly to a scanner listener.
  • !
    The allow_file_and_shm_inputs option defaults to true in 4.1.5 (with a startup warning on every TCP listener), but will default to false in the next major release — TCP clients supplying file paths or shared-memory inputs must migrate to a unix socket before that release.
  • !
    The gpt module's condition callback in local.d/gpt.conf must now return only a boolean and an optional reason string — callbacks that also return content will have that content silently ignored.
  • !
    The Elastic module's flat fuzzy field is replaced by structured per-match objects; saved searches, dashboards, and ingest pipelines referencing the old flat field must be updated, and indices created after the upgrade use the new mapping shape while pre-upgrade indices retain the old one.
  • !
    HFILTER_HELO_IP_A and URI_COUNT_ODD now fire in cases where they previously did not — local score overrides and composites involving these symbols may produce different scores after upgrade.
  • !
    GPT: The condition callback now returns only a boolean; request content generation has been moved into gpt_check.
  • !
    Workers: allow_file_and_shm_inputs now ships as an explicit true default for the normal, controller, and proxy workers — the default will become false in the next major release.
Was this useful?
Cloud & Container Security
◆  Cloud Security Posture

Sysdig Secure

Sources Changelog → 1 release · 2026-08-16 Changelog

Sysdig Secure is a container security platform providing runtime monitoring, vulnerability scanning, and compliance enforcement for cloud-native applications.

Sysdig Secure adds new drill-down views for vulnerability findings—policy evaluation and image layer analysis—plus CISCISA nonprofit that publishes consensus-based configuration benchmarks and controls for hardening operating systems, cloud environments, and software; cyber tools use it as a ready-made compliance baseline. benchmark automation via CNI plugin detection and base image allow/deny list enforcement in the CLI Scanner.

└──▷ WHAT SHIPPED · 2 FEATURES 0 OF 2 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Image layer view and filter in Vulnerability Findings new 75

Adds a Layers tab to the Resource Details drawer for container image resources, showing the image layer stack grouped by base image or Application Layers, with the Dockerfile instruction and per-severity vulnerability counts per layer. Also adds a Layer filter to the CVE list in Vulnerability Findings so findings can be sliced directly by image layer.

— Names tab, filter and grouping mechanism changelog-20260816-3c434e60
02 00
CNI plugin detection for CIS benchmark automation new 75

KSPMKSPMKubernetes Security Posture Management: a category of tooling that continuously audits Kubernetes clusters against configuration best practices and compliance policies to surface misconfigurations before attackers exploit them. Analyzer v1.49.3 adds detection of Container Network Interface (CNI) plugins in use on each Kubernetes node, enabling automatic evaluation of CIS KubernetesCIS KubernetesHardening benchmarks published by the Center for Internet Security for Kubernetes clusters, giving cyber tools a concrete, versioned checklist of configuration checks to run and report against. Benchmark v2.0.0 recommendation 5.3.1 without manual attestation.

— Names version and exact benchmark recommendation, no UI path changelog-20260816-3c434e60
└──▷ ALSO FROM THESE RELEASES
Was this useful?
◆  Runtime Security

Alibaba Cloud OpenSandbox

Sources Release notes → 1 release · 2026-08-13 Notes

Secure, Fast, and Extensible Sandbox runtime for AI agents.

OpenSandbox's execd v1.0.22 release adds background job execution with status polling, read-only PTY viewing, SDK session reattachment, and finer-grained isolation-mode probing, while tightening private-network sessions to fail closed at startup.

└──▷ WHAT SHIPPED · 5 FEATURES 1 OF 5 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Background runs with status polling new 90

The run API now accepts background: true, returning a JSON handle so long-running sessions don't block the caller. New runs/{runId} and runs/{runId}/logs endpoints let callers poll status and stream logs for these background jobs.

Submit a long-running job in the background and poll its status without holding an open connection.
$ # Start a background run
curl -X POST https://execd/run \
  -H 'Content-Type: application/json' \
  -d '{"background": true, "command": "python train.py"}'

# Poll status using the returned runId
curl https://execd/runs/<runId>

# Stream logs
curl https://execd/runs/<runId>/logs
— Runnable curl example against named endpoints and flag. docker/execd/v1.0.22
02 00
SDK session reattachment via attach() new 75

All five SDKs gain attach(sessionId), which rebuilds a fully functional session handle from a bare session ID (e.g. after a worker restart). SessionState now echoes the session's original creation parameters.

Reconnect to an existing session from SDK code after a worker restart, without needing the original session object.
python
session = client.attach(sessionId)
— Code example plus named method and field. docker/execd/v1.0.22
03 00
Per-mode uid isolation probing improved 75

execd now independently probes setpriv/userns support via uid_mode availability checks, returning 503 NOT_SUPPORTED for unavailable isolation modes instead of failing all isolation globally when one mode is unsupported.

— Named mechanism and status code, no example command. docker/execd/v1.0.22
04 01
Private-network sessions fail closed at startup breaking 70

Sessions created with share_net: false now bind-pin the workload NetNS/UserNS and return a retryable 503 on failure; previously a bind-pin failure did not block session creation, but now it fails closed at startup.

— Clear before/after and config key, no runnable example. docker/execd/v1.0.22
05 00
Read-only PTY viewer mode new 65

A new ?mode=viewer query parameter on PTY sessions lets multiple read-only clients watch a live PTY alongside the exclusive holder, supporting replay, live output, and backpressure isolation between viewers.

— Named query param but no worked example given. docker/execd/v1.0.22
└──▷ BREAKING ON UPGRADE
  • !
    share_net: false sessions now fail closed at startup: execd must successfully bind-pin the workload NetNS/UserNS or it returns a retryable 503; previously, failure did not block session creation.
Was this useful?
Identity, Access & Data Protection
◆  Secure Access (VPN / SASE / ZTNA)

Twingate

Sources Changelog → 1 release · 2026-08-16 Changelog

Twingate is a zero-trust network access platform that securely connects remote users and devices to private resources without VPN.

Twingate added HTTP web app protection that injects identity headers into requests, plus a new scoped Helpdesk admin role for support staff.

└──▷ WHAT SHIPPED · 2 FEATURES 0 OF 2 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
HTTP web app protection with JWT/header injection new 53

Twingate now injects a JWTJWTAn open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object passed between parties. Cyber tools use it to verify identity and permissions without querying a central session store. identifying the user, plus custom headers carrying user and group attributes, into requests sent to protected web apps. This enables integration with both legacy and modern apps without requiring re-authentication at the app layer.

— Explains mechanism but no config keys or endpoints given changelog-20260816-24905ea2
02 00
Helpdesk admin role for scoped support access new 52

A new Helpdesk role can be assigned to support staff, granting read-only access to select Admin Console areas plus scoped support actions: resetting MFAMFAMulti-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone., verifying and unverifying devices, and managing trusted serial numbers.

— Names specific permissions but no exact UI path or API changelog-20260816-24905ea2
Was this useful?

Firezone

Sources Changelog → 1 release · 2026-08-16 Changelog

Firezone is an open-source VPN and secure access platform that replaces traditional corporate VPNs with modern zero-trust networking.

Firezone's REST APIREST APIA web API design style where clients interact with resources over HTTP using standard methods like GET, POST, and DELETE, giving cyber tools a predictable, language-agnostic way to integrate with external services. gained a wave of new endpoints for Intune device visibility, resource pool members, and gateway CRUDCRUDThe four basic database operations — Create, Read, Update, Delete — used as shorthand for any system that manages persistent data records, giving cyber tools a standard model for interacting with stored information., plus broad filtering/pagination support across list endpoints, while the desktop/Linux client shipped a headless macOS CLI and doubled Linux tunnel throughput via GRO/GSO.

└──▷ WHAT SHIPPED · 7 FEATURES 2 OF 7 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Query filtering and pagination across list endpoints improved 80

Adds query params for filtering/pagination to a wide set of list endpoints: GET /actors (email, name, type), GET /clients (firezone_id, name), GET /groups (directory_id, entity_type, name), GET /policies (group_id, resource_id), GET /resources (address, ip_stack, name, site_id, type), GET /sites (name), GET /sites/{site_id}/gateways (ipv4, ipv6, name), and the identity provideridentity providerA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems./directory list endpoints GET /email_otp_auth_providers, GET /entra_auth_providers, GET /entra_directories, GET /google_auth_providers, GET /google_directories, GET /oidc_auth_providers, GET /okta_auth_providers, and GET /okta_directories, each of which also gained limit and page_cursor params with a corresponding response schema change for cursor-based pagination.

— Names every endpoint and param but not the pagination mechanics 1.0.0
02 00
Gateway creation and update endpoints new 71

Adds POST /sites/{site_id}/gateways to create a gateway within a site, plus PATCH /sites/{site_id}/gateways/{id} and PUT /sites/{site_id}/gateways/{id} to update an existing gateway; the corresponding GET/DELETE /sites/{site_id}/gateways/{id} response schemas also changed to match.

— Full CRUD surface named, exact methods and paths given 1.0.0
03 00
Intune device integration endpoints new 65

Adds GET /intune_devices, GET /intune_devices/{id}, and GET /intune_integration endpoints, providing read access to Microsoft Intune-managed device records and integration status via the Firezone REST API.

— Endpoints named but no detail on payload or use case 1.0.0
04 00
Resource pool member endpoints new 65

Adds GET /resources/{resource_id}/pool_members, PATCH /resources/{resource_id}/pool_members, and PUT /resources/{resource_id}/pool_members to read and update the pool members associated with a resource.

— Endpoints named but pool-member semantics unexplained 1.0.0
thinner coverage below
05 00
Linux tunnel throughput via GRO/GSO improved 57

Enables GRO and GSO on the TUNTUNA virtual network device in Linux (and other OSes) that lets a userspace program read and write raw IP packets, making it the standard building block for VPNs and traffic-manipulation tools. device on Linux kernels 6.2 and later, roughly doubling single-stream TCPTCPA network protocol that delivers a reliable, ordered stream of bytes between two endpoints. It detects lost data and retransmits it. throughput through the tunnel (1.6.0, #14011).

— Clear mechanism and measured impact, but no user-facing config changelog-20260816-c695dd5c
06 01
Schema changes to actors, policies and resources endpoints breaking 50

Request bodies changed for PATCH /actors/{id} and PUT /actors/{id}; request and/or response schemas changed for POST /policies, PATCH /policies/{id}, PUT /policies/{id}, DELETE /policies/{id}, and GET /policies/{id}; and request bodies changed for POST /resources, PATCH /resources/{id}, and PUT /resources/{id}. No field-level detail on what changed is given.

— Endpoints named but nothing on what fields actually changed 1.0.0
07 02
firezone-cli for headless macOS management new 35

Firezone 1.5.19 adds firezone-cli for headless macOS management.

— Named tool but no commands, flags or usage shown changelog-20260816-c695dd5c
Was this useful?
◆  Identity & Access Management

Nudge Security

Sources Changelog → 1 release · 2026-08-16 Changelog

Nudge Security monitors SaaS application usage and security risks across organizations to reduce cloud infrastructure threats.

Nudge Security shipped a new risk-scoring dashboard, a dedicated passkeypasskeyPhishing-resistant sign-in credentials built on FIDO2/WebAuthn: the device holds a private key and proves possession instead of the user typing a password. They sync across a user's devices. adoption dashboard, and an in-browser nudge that intercepts sensitive data before it reaches AI tools, with an optional enforcement mode.

└──▷ WHAT SHIPPED · 3 FEATURES 1 OF 3 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 01
In-browser AI data-loss nudge with enforcement new 80

A new in-browser nudge, configured under Settings > In-browser nudges, intercepts sensitive data (PIIPIIPersonally Identifiable Information — data that can identify a specific individual, such as names, email addresses, or SSNs. Cyber tools flag or redact it to limit exposure and meet privacy regulations., secrets, financial info) detected in AI-tool conversations, shows the employee exactly what was found, and offers one-click redaction. An optional enforcement mode blocks sending until the sensitive data is redacted.

Prevent unredacted PII or secrets from reaching AI tools across your org by enabling enforcement mode for in-browser nudges.
📍In the Nudge Security console, go to Settings › In-browser nudges, enable sensitive data nudges, then turn on enforce redaction so employees cannot send AI conversations containing detected sensitive data without redacting it first.
— Named config path and enforcement toggle with usage steps changelog-20260816-699c2889
02 00
Passkey adoption dashboard and per-user tracking new 73

The new Dashboards > Passkey usage dashboard, populated by the browser extension, surfaces passkey adoption rate, top apps using passkeyspasskeysPhishing-resistant sign-in credentials built on FIDO2/WebAuthn: the device holds a private key and proves possession instead of the user typing a password. They sync across a user's devices., a storage provider breakdown toggleable between passkey count and user count, device-loss survivability, and per-login verification status. Passkey usage is also now shown per individual employee on their user details page.

Audit where your organization's passkeys are stored and whether they survive device loss — useful before rolling out a passwordless policy.
📍In the Nudge Security console, go to Dashboards › Passkey usage. Toggle the storage-provider breakdown between number of passkeys and number of users, then click an individual employee row to verify their passkey is device-independent and that the user was verified at login.
— Exact UI path and toggle named, with a walkthrough example changelog-20260816-699c2889
03 00
Risk dashboard with residual risk scoring new 70

The new Dashboards > Risk dashboard (open beta) shows residual risk scores, a trend chart filterable to business-critical apps, a business-criticality-vs-residual-risk matrix with drill-down, and a ranked highest-risk-apps table built automatically from Nudge's per-app risk scoring.

— UI path and named components given, no scoring mechanism detail changelog-20260816-699c2889
Was this useful?
Build
◆  AI Coding Agents

Daytona

Sources Release page → 1 release · seen 2026-08-16 Notes

Daytona is a development environment platform that enables standardized, reproducible coding spaces for teams and AI agents.

Daytona tightened security in this release with restricted CLI config file permissions and enforced TLS verification in its Ruby Socket.IO client.

└──▷ WHAT SHIPPED · 1 FEATURE 1 OF 1 FEATURE most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 01
TLS verification enforced in Ruby Socket.IO client breaking 25

TLS verification is now enforced in the Ruby Socket.IO client.

— States the change but no mechanism or migration detail. snapshot-20260816
Was this useful?

OpenAI Codex CLI

Sources Release notes →Source code → 1 release · 2026-08-16 Notes Code

Lightweight coding agent that runs in your terminal

Codex CLI's alpha channel added disk-space and Windows Dev Drive diagnostics to codex doctor, non-blocking environment attachment configuration for threads, and W3C trace-context propagation through exec-server relay frames, alongside smaller TUITUIA text-based user interface that runs inside a terminal, using characters and ANSI escape codes to render menus, panes, and widgets without a graphical desktop, letting cyber tools ship rich interactivity with no GUI dependency., exec-thread, and gRPCgRPCAn open-source remote procedure call framework from Google that uses HTTP/2 and Protocol Buffers to let services call each other's functions across a network, giving tools low-latency, strongly typed inter-process communication. health-check improvements.

└──▷ WHAT SHIPPED · 0 FEATURES7 FEATURES 0 OF 7 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Disk space and Dev Drive checks in codex doctor new 73

codex doctor now checks free disk space for both CODEX_HOME and the current worktree, showing a warning below a 5 GiB threshold and failing below 1 GiB; on Windows targets it also checks for a Dev Drive.

— Names the exact command and thresholds; run `codex doctor` to see it. rust-v0.148.0-alpha.20
02 00
Non-blocking pending environment attachment for threads new 70

Threads can now start without blocking while environment attachment configuration is still pending, while ensuring turns do not use an attachment prematurely; adds a Failed configuration state and an environment_failed callback for per-thread failure and recovery.

— Describes mechanism and names the new state and callback, no usage steps. rust-v0.148.0-alpha.20
03 00
Trace context propagation through exec-server relay improved 60

Propagates W3C traceparent and tracestate trace context through exec-server relay frames, including fragmented encrypted Noise requests.

— Names exact headers and mechanism but is internal, not directly actionable. rust-v0.148.0-alpha.20
thinner coverage below
04 00
Health endpoint on code-mode gRPC listener new 40

Adds a health endpoint to the code-mode gRPC listener.

— Names the exact surface added but no path or usage example given. rust-v0.148.0-alpha.20
05 00
TUI startup and context state improvements improved 35

TUI app directory state is now scoped to the active context, and the TUI shows resume and fork status during startup.

— Thin descriptions of two small TUI behavior changes. rust-v0.148.0-alpha.20
06 00
Workload identity context in token exchange improved 35

Forwards workload identityworkload identityAn identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials. context during token exchangetoken exchangeAn OAuth 2.0 protocol extension (RFC 8693) that lets a service trade one token for another with different scopes, audience, or type, enabling delegation and impersonation across service boundaries without re-authenticating the user..

— Names the mechanism briefly but lacks further detail. rust-v0.148.0-alpha.20
07 00
Paginated history for persistent exec threads improved 25

Persistent exec threads now use paginated history.

— One-line description with no mechanism or usage detail. rust-v0.148.0-alpha.20
Was this useful?
Deploy
◆  Local LLM Runtimes

vMLX

Sources Release notes → 1 release · 2026-08-15 Notes

vMLX - JANGTQ Uber Compressed MLX Models - L2 Disk Cache (survives restart) + L1 Paged (super fast ttft) + Hybrid SSM Scheduler + Cont Batching + etc!

vMLX 1.6.29 focuses on cache reuse across long-context and multiturn workloads, adding a hybrid prefix cache for much faster follow-up turns and a default-on chunked SSM re-derive path that restores cache reuse at scale, alongside verification across a dozen model families.

└──▷ WHAT SHIPPED · 3 FEATURES 0 OF 3 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Chunked SSM re-derive and long-context cache stability improved 73

Chunked SSM re-derive ships enabled by default, restoring long-context cache reuse from 0% to 99.9% above 12.5k tokens on hybrid SSM model families. This was validated with a 100k-context multiturn test where a 97.6k-token conversation retrieved planted facts with 99.9% cache reuse and no memory faults.

— Detailed metrics and default behavior, but no user-facing control named v1.6.29
02 00
Hybrid prefix cache for long-document follow-ups new 63

A hybrid prefix cache delivers up to 20x faster follow-up turns on long documents: a 43.7k-token document follow-up drops from 107s to 5s, with output byte-identical at temperature 0.

— Concrete before/after numbers but no flag or config to invoke it v1.6.29
thinner coverage below
03 00
Per-family cache and generation hardening improved 50

Cache, parser, and generation-default hardening was verified across 12 model families, including DSV4 Flash native composite caching, Gemma 4 mixed-SWA with audio, Qwen 3.6/3.8 hybrid lines with native MTP, and TurboQuant KV bundles.

— Names families tested but no actionable steps or config given v1.6.29
Was this useful?
Govern
◆  AI/LLM Security

Certiv

Sources Release page → 1 release · seen 2026-08-16 Notes

Certiv is an AI-powered code security platform that identifies and remediates vulnerabilities in software applications.

Certiv shipped a new Privacy Mode that ties agent session visibility to policy risk with auditable access logging, alongside its first published API for lead-capture endpoints.

└──▷ WHAT SHIPPED · 2 FEATURES 0 OF 2 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Privacy Mode for agent session visibility new 72

Privacy Mode changes session visibility defaults so only sessions with policy violations are automatically surfaced to security teams, while compliant sessions stay private unless an authorized user records an explicit justification for access. Certiv logs who accessed a private compliant session and the recorded reason, creating an auditable trail for governance, privacy teams, and works councils. It integrates with the existing Policy Engine and Scout endpoint observer, so policy verdict determines session visibility without altering real-time Block, Pause, and Steer interventions. Privacy Mode is now available in Preview to existing Certiv customers, enabled on request through the Certiv team.

— Mechanism and integration points clear, but enablement is a support request, not a config key. Enterprise Security with Privacy by Design: …
thinner coverage below
02 00
Public API with lead capture endpoints new 38

Certiv now publishes an API covering one area, Lead Capture, with 2 public endpoints for requesting a demo or subscribing to the newsletter.

— Endpoint count and purpose given but no methods or paths named. 1.0.0
Was this useful?

NVIDIA SkillSpector

Sources Release notes → 1 release · 2026-08-15 Notes

Security scanner for AI agent skills. Detect vulnerabilities, malicious patterns, security risks, prompt injection, data exfiltration, and supply-chain risks in Claude Code, Codex, and MCP skills before you install them.

SkillSpector v2.9.5 adds support for three new inference providers, opt-in baseline auto-discovery, and static detection for insecure deserializationdeserializationTurning stored or transmitted data back into objects a program can use. Unsafe handling of untrusted data can allow unexpected behavior or code execution., alongside two YARA matching accuracy fixes.

└──▷ WHAT SHIPPED · 5 FEATURES 0 OF 5 FEATURES most completely described first
what's the number?

Each feature carries 0–100 for how completely the vendor documented it — not how big or important the work is. A major capability described in eight words scores low, and that is the finding.

  • depth0–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point

Code and config rank first by construction: a documented endpoint, flag or config key scores at the top of specificity and actionability, so it sorts above a feature described only in prose. Under 60 the notes go thin — everything below the “thinner coverage” line is thinner documentation, not smaller work. Hover any meter for that feature's three sub-scores.

01 00
Auto-discovery of baseline config file new 60

Adds opt-in auto-discovery of a top-level .skillspector-baseline.yaml file, keeping explicitly supplied baselines authoritative when both are present.

— Names exact config file and precedence behavior v2.9.5
thinner coverage below
02 00
Static detection for insecure deserialization new 50

Adds static analyzer coverage for insecure deserialization patterns represented by findings AST10, TT6, DS1, DS2, DS3, and DS4.

— Lists specific finding codes but no detection mechanism detail v2.9.5
03 00
Ollama, Azure OpenAI, and generic OpenAI-compatible providers new 45

Adds Ollama support for local OpenAI-compatible inference, Azure OpenAI deployment routing, and a configurable provider for generic OpenAI-compatible endpoints.

— Names three providers but no config keys or setup steps v2.9.5
04 00
YARA post-filter rule namespace scoping improved 45

Scopes the destructive-autonomy YARA post-filter to SkillSpector's built-in rule namespace and preserves deterministic built-in rule precedence, preventing custom YARA rules that reuse a built-in rule name from being incorrectly post-filtered.

— Clear mechanism and fixed bug scenario, no direct user action v2.9.5
05 00
Byte-offset YARA match line mapping improved 40

Switches YARA match-to-source-line mapping to byte offsets so non-ASCII content is reported at accurate locations.

— Explains before/after but no user-facing action v2.9.5
Was this useful?
browse all tools → score card for your toolchain →