api/v1.7.0
api/v1.7.0 release
First reported Apr 29, 2026 13:29 UTCCatalog metadata updated Oct 13, 2026 01:46 UTCOpen evidence recordPublished file metadata, source observations, indicators, and research history in one bounded catalog.
Sources represented on this page. Publication and observation dates describe the content; successful batch dates describe local collection. A recent batch does not certify complete coverage or current provider availability.
3 sources: 0 stale, 0 needing attention, 0 paused, 0 unverified.
Stale means older than twice the recorded collection interval, with a minimum of one hour; without an interval, the threshold is 24 hours. Cached content remains available while a feed is stale, paused, or unverified.
api/v1.7.0 release
First reported Apr 29, 2026 13:29 UTCCatalog metadata updated Oct 13, 2026 01:46 UTCOpen evidence recordtotal: 738 commits, prs: 253 pr commits: 738 Upgrade notes Read the upgrade notes carefully before upgrading Tetragon. Depending on your setup, changes listed here might require a manual intervention. See the Stack Traces documentation for stack trace migration. Helm Values Change the default server-address of the agent to from localhost:54321 to /var/run/tetragon/tetragon.sock. This socket is also available for root users under the same path on the node. Update this address in all third-party programs that connect to the agent. Events (protobuf API) The legacy stacktrace-tree API has been removed: GetStackTraceTree gRPC, tetra stacktrace-tree CLI command, and related types (GetStackTraceTreeRequest, GetStackTraceTreeResponse, stack.proto). Use TracingPolicy with kernelStackTrace and userStackTrace in the Post action to get stack traces in ProcessKprobe events. See the Stack Traces documentation and examples/tracingpolicy/stack_traces.yaml. The already-deprecated EnableTracingPolicy and DisableTracingPolicy gRPC methods have been actually enforced to return an error when used. For now, enable-deprecated-tracingpolicy-grpc option has been introduced to restore the old behavior. The next release will remove the deprecated methods. Metrics Kprobe and uprobe merge metrics have been consolidated. The following metrics were removed: tetragon_generic_kprobe_merge_errors_total tetragon_generic_kprobe_merge_ok_total They are replaced by tetragon_generic_kprobe_merge_total which includes a status label with values ok or error. The new metric also includes labels curr_type, prev_type (either enter or exit), curr_fn, and prev_fn. Changes Major changes tetragon: Add support to retrieve environment variables (#4184) by @olsajiri tracingpolicy: add matchParentBinaries selector (#4254) by @kobrineli celbpf: evaluate CEL expressions in bpf (#4504) by @kkourt tetragon: Add fentry sensor (#4039) by @olsajiri Add support for spec.hostSelector (#4814) by @tpapagian Bugfixes Fix memory leaks in process and event caches (#4255) by @mtardy feat: allow LSM funcs to be overridden on SLE (#4158) by @holyspectral helm: Handle tetragon.enabled value properly (#4285) by @michi-covalent bug: Avoid overwritten slogLeveler (#4287) by @sayboras Fix LSM sensor failing to load with --enable-cgidmap due to tg_cgtracker_map size mismatch (#4391) by @ariosmon fix(pkg/sensors): fixed ret{k,u}probe_calls map builder invocation. (#4397) by @FedeDP elf: handle spaces found in arm64 stapsdt (#4426) by @andrewstrohman fix(pkg/sensors): fixed {k,u}retprobe args merge helper. (#4494) by @FedeDP uprobe: add support for monitor mode and stats (#4662) by @kkourt fix(grpc/exec): fix RefDec in exit's eventcache path (#4593) by @dwindsor logger: do not ignore time-stamped formats (#4667) by @kkourt fix(pkg/sensors): skip nested ptr detection for indexed array access. (#4519) by @FedeDP add set action stats (#4762) by @kkourt helm: fix rthooks container resources not being applied (#4766) by @PhilipSchmid tetragon: policies can now be loaded even if kptr_restrict is equal to 2 (#4765) by @FedeDP bpf: Fix mnt_namespace RHEL7 fallback writing to wrong field (#4785) by @sayboras Fix tetragon_overhead_program_seconds_total metric to correctly report seconds instead of nanoseconds (#4830) by @danilovid fix(bpf): define _MULTI_KPROBE macro when needed. (#4849) by @FedeDP Fix a infinite loop when using range notation with math.MaxUint64 as upper bound (#4848) by @3u13r pkg/tetragoninfo: read previously ignored value returned by errors.Join in encode configuration function. (#4901) by @mtardy pkg/policyfilter: copy Pod labels to avoid mutations (#4916) by @mtardy fix: handle matchBinaries NotIn when execve_map misses process (#4641) (#4654) by @mann-ds fix: handle matchBinaries NotIn when execve_map misses process (#4641) bpf: zero stale pkey and flags in event_find_curr_probe tests: add matchBinaries NotIn tests for perfring and early-exec cases Add tetragon_process_cache
First reported Apr 29, 2026 17:19 UTCCatalog metadata updated Oct 13, 2026 01:46 UTCOpen evidence recordSigned-off-by: Kornilios Kourtis kornilios@isovalent.com
First reported Apr 29, 2026 14:52 UTCCatalog metadata updated Oct 13, 2026 01:46 UTCOpen evidence recordapi/v1.6.1 release
First reported Mar 31, 2026 17:18 UTCCatalog metadata updated Oct 13, 2026 01:46 UTCOpen evidence recordfix(deps): update module github.com/containerd/containerd to v1.7.29 …
First reported Nov 07, 2025 09:40 UTCCatalog metadata updated Oct 13, 2026 01:46 UTCOpen evidence recordThis change enables preloading string arguments for USDT hooks. A previous commit enabled this on the bpf side. This commit adds the required logic for the user space side. As USDT hooks apply to user space programs, some of the program's memory may not be paged in when the hook fires. Adding this sleep-able program allows us to handle this scenario by triggering page faults as required to facilitate argument reading. Signed-off-by: Andy Strohman astrohma@isovalent.com
First reported Feb 20, 2026 06:47 UTCCatalog metadata updated Oct 13, 2026 01:46 UTCOpen evidence recordChanges from v1.6.0 to v1.6.1 total: 62 commits, prs: 34 pr commits: 62 Upgrade notes No upgrade note for that patch release. Bugfixes [v1.6] Fix memory leaks in process and event caches (#4257) by @mtardy fix(pkg/sensors): fixed kretprobe args merge helper (#4505) by @FedeDP [v1.6 backport] bpf: make op_capabilities_gained filter consistent (#4564) by @andrewstrohman fix(pkg/sensors): cgtrackermap size for uprobe, lsm and usdt sensors (#4586) by @FedeDP fix(process/cache): balance parent refcount ops during LRU eviction (1.6) (#4689) by @dwindsor Update default tetragon-rthooks image tag from v0.5 to v0.8. (#4768) by @will-isovalent tetragon: policies can now be loaded even if kptr_restrict is equal to 2 (#4776) by @FedeDP helm: Handle tetragon.enabled value properly (#4292) by @michi-covalent uprobe: support match args (#4319) by @andrewstrohman [backport/v1.6] Add umode_t in validation (#4338) by @tpapagian uprobes: allow using BTF resolve (#4380) by @andrewstrohman various v1.6 backports 20260219 (#4669) by @kkourt [v1.6] new(bpf,pkg,docs): use tracefs instead of debugfs (#4754) by @FedeDP [backport/v1.6] helm: fix rthooks container resources not being applied (#4775) by @tpapagian bug: Avoid overwritten slogLeveler (#4300) by @sayboras Fixed NotEqual operator for integer matchArgs with multiple values (#4727) by @AritraDey-Dev process: improve exec refcounting (#4473) by @kevsecurity CI changes Makefile: update buf breaking change check to v1.6 branch (#4801) by @dangome3 fixes backports (#4318) by @olsajiri [v1.6] tetragon: Fix TestMatchBinariesFollowChildrenUpdate test (#4514) by @olsajiri [v1.6] Revert "ci: Fix package e2e tests GHA" (#4695) by @andrewstrohman Backports/kevsecurity/v1.6/improve ring reliability in tests (#4268) by @kevsecurity Backports/v1.6: tetragon: Limit sys_close events in test (#4271) by @kevsecurity Makefile: don't rely on PWD (#4782) by @dangome3 Dependency updates fix(deps): update module github.com/cilium/ebpf to v0.20.0 (#4688) by @sayboras fix(deps): update module github.com/containerd/containerd to v1.7.29 [security] (v1.6) (#4305) by @cilium-renovate[bot] chore(deps): update docker.io/library/alpine docker tag to v3.23.0 (v1.6) (#4413) by @cilium-renovate[bot] chore(deps): update docker.io/library/alpine docker tag to v3.23.2 (v1.6) (#4453) by @cilium-renovate[bot] chore(deps): update docker.io/library/alpine docker tag to v3.23.3 (v1.6) (#4592) by @cilium-renovate[bot] chore(deps): update module golang.org/x/net to v0.45.0 [security] (v1.6) (#4614) by @cilium-renovate[bot] chore(deps): update go to v1.25.8 (v1.6) (patch) (#4793) by @cilium-renovate[bot] fix(deps): update module google.golang.org/grpc to v1.79.3 [security] (v1.6) (#4773) by @cilium-renovate[bot] Full Changelog: v1.6.0...v1.6.1
First reported Mar 31, 2026 17:48 UTCCatalog metadata updated Oct 13, 2026 01:46 UTCOpen evidence recordChangelog fb5d707 thats a paddlin 50493db feat: document stdout report path (#1990)
First reported Nov 19, 2025 21:22 UTCCatalog metadata updated Oct 13, 2026 01:42 UTCOpen evidence recordChangelog 83d9cd6 update goreleaser 8d1f98c Removed unnecessary functions from report template (#2040) ca20267 its the simple things (#2020) b66ac75 build: switch to Go 1.24 (#2002)
First reported Mar 21, 2026 02:20 UTCCatalog metadata updated Oct 13, 2026 01:42 UTCOpen evidence recordChangelog c7acf33 Merge branch 'master' of github.com:gitleaks/gitleaks 9faaa4a Add experimental allowlist optimizations (#1731) 79068b3 Detect Notion Public API Keys #1889 (#1890)
First reported Jun 09, 2025 00:42 UTCCatalog metadata updated Oct 13, 2026 01:42 UTCOpen evidence recordChangelog 6eaad03 0 to 5 - notes on recursive decoding (#1994) 09242ce Add new Looker client ID and client secret rules (#1947) c98e5e0 feat: add Airtable Personnal Access Token detection (#1952) 4ed0ca4 build: upgrade Go & alpine version (#1989)
First reported Nov 26, 2025 18:08 UTCCatalog metadata updated Oct 13, 2026 01:42 UTCOpen evidence recordChangelog 80468ef Merge branch 'master' of github.com:gitleaks/gitleaks ef82237 fix(atlassian): reduce false-positives for v1 pattern (#1892) 2463f11 Fix log suppresion issue (#1887) 6f251ee Added Heroku API Key New Version (#1883) 20f9a1d Add Platform Bitbucket (#1886) 722ce82 Add Platform Gitea (#1884) 79780b8 Merge branch 'master' of github.com:gitleaks/gitleaks c5683ca prevent default warn message when max-archive-depth not set (#1881) 0357c3c prevent default warn message when max-archive-depth not set
First reported Jun 08, 2025 02:03 UTCCatalog metadata updated Oct 13, 2026 01:42 UTCOpen evidence recordChangelog ed65b65 Add trace log for skipped archive file when not enabled (#1961) c5ccbb9 Respect contexts with timeouts (#1948) 3821f30 Config min version (#1955) d223718 fix(config): validate rules when [extend] is used (#1592) 87d9629 feat: add Amazon Bedrock API key detection (#1935) 228396b Add GitHub Sponsors section and Discord link a82bc53 feat: improve regex to detect Sonar tokens with prefixes (#1931)
First reported Nov 05, 2025 01:23 UTCCatalog metadata updated Oct 13, 2026 01:42 UTCOpen evidence recordChangelog 78eebac Percent/URL Decoding Support (#1831) 6f967ca fix(kubernetes): remove slow element from pat (#1848) 88f56d3 feat: identify slow file (#1479) 9609928 rm 1password detect test since we test it in cfg gen 23cb69f feat(rules): Add 1Password secret key detection (#1834) Calling this one @bplaxco's release as he introduced a really clever method for mixed decoding without sacrificing too much performance. As I stated in his PR, I think he's either a wizard or some time traveling AI. Dude is wicked smaht Anyways, Gitleaks now supports the following decoders: hex, percent(url enconding), and b64. It's relatively straight forward to add a new decoder so if you're motivated, community contributions are welcomed! Here's an example: ~/code/gitleaks-org/gitleaks (master) cat decode.txt text below aGVsbG8sIHdvcmxkIQ%3D%3D%0A text above ~/code/gitleaks-org/gitleaks (master) ./gitleaks dir decode.txt --max-decode-depth=2 --log-level=debug ○ │╲ │ ○ ○ ░ ░ gitleaks 4:08PM DBG using stdlib regex engine 4:08PM DBG unable to load gitleaks config from decode.txt/.gitleaks.toml since --source=decode.txt is a file, using default config 4:08PM DBG found .gitleaksignore file: .gitleaksignore 4:08PM DBG segment found: original=[29,38] pos=[29,38]: "%3D%3D%0A" -> "==\n" 4:08PM DBG segment found: original=[11,38] pos=[11,31]: "aGVsbG8sIHdvcmxkIQ==" -> "hello, world!" 4:08PM INF scanned ~50 bytes (50 bytes) in 1.5ms 4:08PM INF no leaks found
First reported May 12, 2025 21:13 UTCCatalog metadata updated Oct 13, 2026 01:42 UTCOpen evidence recordChangelog d1c7759 fix(detect): test all allowlists (#1845) Big thanks @rgmz
First reported Apr 30, 2025 13:52 UTCCatalog metadata updated Oct 13, 2026 01:42 UTCOpen evidence recordChangelog 4fb4382 cant count b1c9c7e Composite rules (#1905) 72977e4 feat: add Anthropic API key detection (#1910) 7b02c98 fix(git): handle port (#1912) 2a7bcff dont prematurely calculate fragment newlines (#1909) bd79c3e feat(allowlist): promote optimizations (#1908) 7fb4eda Fix: CVEs on go and go crypto (#1868) a044b81 feat: add artifactory reference token and api key detection (#1906) bf380d4 silly f487f85 Update gitleaks.yml 958f55a add just like that, no leaks Optimizations #1909 waits to find newlines until a match. This ends up saving a boat load of time since before we were finding newlines for every fragment regardless if a rule matched or not. #1908 promoted @rgmz excellent stopword optimization Composite Rules (Multi-part or required Rules) #1905 In v8.28.0 Gitleaks introduced composite rules, which are made up of a single "primary" rule and one or more auxiliary or required rules. To create a composite rule, add a [[rules.required]] table to the primary rule specifying an id and optionally withinLines and/or withinColumns proximity constraints. A fragment is a chunk of content that Gitleaks processes at once (typically a file, part of a file, or git diff), and proximity matching instructs the primary rule to only report a finding if the auxiliary required rules also find matches within the specified area of the fragment. Proximity matching: Using the withinLines and withinColumns fields instructs the primary rule to only report a finding if the auxiliary required rules also find matches within the specified proximity. You can set: withinLines: N - required findings must be within N lines (vertically) withinColumns: N - required findings must be within N characters (horizontally) Both - creates a rectangular search area (both constraints must be satisfied) Neither - fragment-level matching (required findings can be anywhere in the same fragment) Here are diagrams illustrating each proximity behavior: p = primary captured secret a = auxiliary (required) captured secret fragment = section of data gitleaks is looking at *Fragment-level proximity* Any required finding in the fragment ┌────────┐ ┌──────┤fragment├─────┐ │ └──────┬─┤ │ ┌───────┐ │ │a│◀────┼─│✓ MATCH│ │ ┌─┐└─┘ │ └───────┘ │┌─┐ │p│ │ ││a│ ┌─┐└─┘ │ ┌───────┐ │└─┘ │a│◀──────────┼─│✓ MATCH│ └─▲─────┴─┴───────────┘ └───────┘ │ ┌───────┐ └────│✓ MATCH│ └───────┘ *Column bounded proximity* `withinColumns = 3` ┌────────┐ ┌────┬─┤fragment├─┬───┐ │ └──────┬─┤ │ ┌───────────┐ │ │ │a│◀┼───┼─│+1C ✓ MATCH│ │ ┌─┐└─┘ │ └───────────┘ │┌─┐ │ │p│ │ │ ┌──▶│a│ ┌─┐ └─┘ │ ┌───────────┐ │ │└─┘ ││a│◀────────┼───┼─│-2C ✓ MATCH│ │ │ ┘ │ └───────────┘ │ └── -3C ───0C─── +3C ─┘
First reported Jul 20, 2025 16:24 UTCCatalog metadata updated Oct 13, 2026 01:42 UTCOpen evidence recordChangelog 782f310 Archive support (#1872) 489d13c Update README.md d29ee55 Reduce aws-access-token false positives (#1876) 611db65 Set pass_filenames to false for Docker hook (#1850) 0589ae0 unicode decoding (#1854) 82f7e32 Diagnostics (#1856) f97a9ee chore: include decoder in debug log (#1853) Got another @bplaxco release. Cheers! Archive Scanning Sometimes secrets are packaged within archive files like zip files or tarballs, making them difficult to discover. Now you can tell gitleaks to automatically extract and scan the contents of archives. The flag --max-archive-depth enables this feature for both dir and git scan types. The default value of "0" means this feature is disabled by default. Recursive scanning is supported since archives can also contain other archives. The --max-archive-depth flag sets the recursion limit. Recursion stops when there are no new archives to extract, so setting a very high max depth just sets the potential to go that deep. It will only go as deep as it needs to. The findings for secrets located within an archive will include the path to the file inside the archive. Inner paths are separated with !. Example finding (shortened for brevity): Finding: DB_PASSWORD=8ae31cacf141669ddfb5da ... File: testdata/archives/nested.tar.gz!archives/files.tar!files/.env.prod Line: 4 Commit: 6e6ee6596d337bb656496425fb98644eb62b4a82 ... Fingerprint: 6e6ee6596d337bb656496425fb98644eb62b4a82:testdata/archives/nested.tar.gz!archives/files.tar!files/.env.prod:generic-api-key:4 Link: https://github.com/leaktk/gitleaks/blob/6e6ee6596d337bb656496425fb98644eb62b4a82/testdata/archives/nested.tar.gz This means a secret was detected on line 4 of files/.env.prod. which is in archives/files.tar which is in testdata/archives/nested.tar.gz. Currently supported formats: The compression and archive formats supported by mholt's archives package are supported.
First reported Jun 01, 2025 16:43 UTCCatalog metadata updated Oct 13, 2026 01:42 UTCOpen evidence recordToday, Ivanti published an advisory.“No way?” we hear you say. "Yes way!"Today’s advisory outlines two vulnerabilities in Ivanti’s Sentry product, appealing directly to our inner desire for sophisticated server-side, pre-authenticated vulnerabilities.CVE-2026-10520An OS Command Injection
First reported Jun 10, 2026 00:52 UTCCatalog metadata updated Oct 13, 2026 01:40 UTCOpen evidence recordThree posts? In three days? Are we insane?We're home alone, there's no one to stop us, and we're up past bedtime. So, we need to talk about Splunk. On June 10th, Splunk published this CVE-2026-20253 advisory:It has everything that we
First reported Jun 12, 2026 20:35 UTCCatalog metadata updated Oct 13, 2026 01:40 UTCOpen evidence recordIf you squint and look at the CISA KEV list, you might think it's made up exclusively of vulnerabilities in file transfer solutions.While this would be wrong (and you shouldn’t squint, it’s bad for your eyes), file transfer solutions do play a decent
First reported Apr 02, 2026 10:00 UTCCatalog metadata updated Oct 13, 2026 01:40 UTCOpen evidence recordWelcome back to another watchTowr Labs blog post.This time, we're looking at Progress Kemp LoadMaster, a load balancer that sits at the edge of a lot of enterprise networks. Edge appliances have a habit of becoming the way in rather than the thing keeping people out, and
First reported Jun 29, 2026 19:24 UTCCatalog metadata updated Oct 13, 2026 01:40 UTCOpen evidence recordIt is yet another day in this parallel universe of security, where the devices we bolt onto the edge of our networks to keep the bad people out are, with remarkable consistency, the exact thing that let the bad people in.While we’ve seemingly had a breather from
First reported Jun 12, 2026 05:17 UTCCatalog metadata updated Oct 13, 2026 01:40 UTCOpen evidence recordToday, we woke up with a nagging feeling: what if Citrix had, in fact, patched multiple Memory Overread vulnerabilities as part of CVE-2026-3055? While we've been using our analysis from Part 1 (please read it first, as this post will be brief) to accurately identify exploitable
First reported Mar 29, 2026 20:07 UTCCatalog metadata updated Oct 13, 2026 01:40 UTCOpen evidence recordGod damn it, we're back in the room again. Yes, that sound in your ears is screaming. The footgun has gone off again, shockingly, and we are yet again dealing with a situation where the entire world apparently knew about Citrix NetScaler CVEs before Citrix had woken up
First reported Sep 28, 2026 10:55 UTCCatalog metadata updated Oct 13, 2026 01:40 UTCOpen evidence recordThe public shared-host view reaches the newest 2,400 matching records. Narrow the filters or search an exact MD5, SHA-1, or SHA-256 value to reach a specific record.
A filename, label, or report mention alone does not establish maliciousness. Observation dates describe cited sources; collection dates describe this local metadata catalog. No malware samples are stored, fetched, or executed by these pages.