Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.61% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2025
CVE-2025-29786High confidence
Memory Exhaustion in Expr Parser with Unrestricted Input
expr-lang · expr
Official source article: GitHub GHSA-93MQ-9FFX-83M2 ↗. Check the applicable product and release in the original source.
7.5HighCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs expr-lang expr and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Debian Security Tracker: 4 affected package states with no published fix
Distribution package intelligence
5 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | golang-github-antonmedv-expr | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian bookwormbookworm · source | golang-github-antonmedv-expr | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian forkyforky · source | golang-github-antonmedv-expr | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian sidsid · source | golang-github-antonmedv-expr | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | golang-github-antonmedv-expr | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 7 Oct 2026 |
Open-source package ranges2 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Gogithub.com/expr-lang/expr | SEMVER: introduced 0; fixed 1.17.0 | 1.17.0 | OSV record ↗aggregator derived · 10 Sep 2026 |
| gogithub.com/expr-lang/expr | < 1.17.0 | 1.17.0 | GitHub advisory ↗upstream repository advisory · 17 Mar 2025 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2025-29786 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitygithub.com/expr-lang/expr: Memory Exhaustion in Expr Parser with Unrestricted Input
The vendor explicitly identifies these products as affected by this CVE.
- custom-metrics-autoscaler/custom-metrics-autoscaler-admission-webhooks-rhel8 as a component of Custom Metric Autoscaler operator for Red Hat Openshift
- custom-metrics-autoscaler/custom-metrics-autoscaler-rhel8 as a component of Custom Metric Autoscaler operator for Red Hat Openshift
- deployment-validation-operator-container as a component of Deployment Validation Operator
- rhoai/odh-data-science-pipelines-argo-argoexec-rhel8 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-data-science-pipelines-argo-workflowcontroller-rhel8 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-ml-pipelines-api-server-v2-rhel8 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-ml-pipelines-driver-rhel8 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-ml-pipelines-launcher-rhel8 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-ml-pipelines-persistenceagent-v2-rhel8 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-ml-pipelines-scheduledworkflow-v2-rhel8 as a component of Red Hat OpenShift AI (RHOAI)
- rhosdt/opentelemetry-operator-bundle as a component of Red Hat OpenShift distributed tracing 3
- rhosdt/opentelemetry-target-allocator-rhel8 as a component of Red Hat OpenShift distributed tracing 3
- Summary
- A flaw was found in Expr. This vulnerability allows excessive memory usage and potential out-of-memory (OOM) crashes via unbounded input strings, where a malicious or inadvertent large expression can cause the parser to construct an extremely large Abstract Syntax Tree (AST), consuming excessive memory.
- Remediation
- Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
Expr is an expression language and expression evaluation for Go. Prior to version 1.17.0, if the Expr expression parser is given an unbounded input string, it will attempt to compile the entire string and generate an Abstract Syntax Tree (AST) node for each part of the expression. In scenarios where input size isn’t limited, a malicious or inadvertent extremely large expression can consume excessive memory as the parser builds a huge AST. This can ultimately lead to*excessive memory usage and an Out-Of-Memory (OOM) crash of the process. This issue is relatively uncommon and will only manifest when there are no restrictions on the input size, i.e. the expression length is allowed to grow arbitrarily large. In typical use cases where inputs are bounded or validated, this problem would not occur. The problem has been patched in the latest versions of the Expr library. The fix introduces compile-time limits on the number of AST nodes and memory usage during parsing, preventing any single expression from exhausting resources. Users should upgrade to Expr version 1.17.0 or later, as this release includes the new node budget and memory limit safeguards. Upgrading to v1.17.0 ensures that extremely deep or large expressions are detected and safely aborted during compilation, avoiding the OOM condition. For users who cannot immediately upgrade, the recommended workaround is to impose an input size restriction before parsing. In practice, this means validating or limiting the length of expression strings that your application will accept. For example, set a maximum allowable number of characters (or nodes) for any expression and reject or truncate inputs that exceed this limit. By ensuring no unbounded-length expression is ever fed into the parser, one can prevent the parser from constructing a pathologically large AST and avoid potential memory exhaustion. In short, pre-validate and cap input size as a safeguard in the absence of the patch.
What
Expr is an expression language and expression evaluation for Go. Prior to version 1.17.0, if the Expr expression parser is given an unbounded input string, it will attempt to compile the entire string and generate an Abstract Syntax Tree (AST) node for each part of the expression. In scenarios where input size isn’t limited, a malicious or inadvertent extremely large expression can consume excessive memory as the parser builds a huge AST. This can ultimately lead to*excessive memory usage and an Out-Of-Memory (OOM) crash of the process. This issue is relatively uncommon and will only manifest when there are no restrictions on the input size, i.e. the expression length is allowed to grow arbitrarily large. In typical use cases where inputs are bounded or validated, this problem would not occur. The problem has been patched in the latest versions of the Expr library. The fix introduces compile-time limits on the number of AST nodes and memory usage during parsing, preventing any single expression from exhausting resources. Users should upgrade to Expr version 1.17.0 or later, as this release includes the new node budget and memory limit safeguards. Upgrading to v1.17.0 ensures that extremely deep or large expressions are detected and safely aborted during compilation, avoiding the OOM condition. For users who cannot immediately upgrade, the recommended workaround is to impose an input size restriction before parsing. In practice, this means validating or limiting the length of expression strings that your application will accept. For example, set a maximum allowable number of characters (or nodes) for any expression and reject or truncate inputs that exceed this limit. By ensuring no unbounded-length expression is ever fed into the parser, one can prevent the parser from constructing a pathologically large AST and avoid potential memory exhaustion. In short, pre-validate and cap input size as a safeguard in the absence of the patch.
Why
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
What
Expr is an expression language and expression evaluation for Go. Prior to version 1.17.0, if the Expr expression parser is given an unbounded input string, it will attempt to compile the entire string and generate an Abstract Syntax Tree (AST) node for each part of the expression. In scenarios where input size isn’t limited, a malicious or inadvertent extremely large expression can consume excessive memory as the parser builds a huge AST. This can ultimately lead to*excessive memory usage and an Out-Of-Memory (OOM) crash of the process. This issue is relatively uncommon and will only manifest when there are no restrictions on the input size, i.e. the expression length is allowed to grow arbitrarily large. In typical use cases where inputs are bounded or validated, this problem would not occur. The problem has been patched in the latest versions of the Expr library. The fix introduces compile-time limits on the number of AST nodes and memory usage during parsing, preventing any single expression from exhausting resources. Users should upgrade to Expr version 1.17.0 or later, as this release includes the new node budget and memory limit safeguards. Upgrading to v1.17.0 ensures that extremely deep or large expressions are detected and safely aborted during compilation, avoiding the OOM condition. For users who cannot immediately upgrade, the recommended workaround is to impose an input size restriction before parsing. In practice, this means validating or limiting the length of expression strings that your application will accept. For example, set a maximum allowable number of characters (or nodes) for any expression and reject or truncate inputs that exceed this limit. By ensuring no unbounded-length expression is ever fed into the parser, one can prevent the parser from constructing a pathologically large AST and avoid potential memory exhaustion. In short, pre-validate and cap input size as a safeguard in the absence of the patch.
Why
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Allocation of Resources Without Limits or Throttling → disrupt the affected service
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-770 ↗
CWE-770: Allocation of Resources Without Limits or Throttling. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- custom-metrics-autoscaler/custom-metrics-autoscaler-admission-webhooks-rhel8 as a component of Custom Metric Autoscaler operator for Red Hat Openshift
- custom-metrics-autoscaler/custom-metrics-autoscaler-rhel8 as a component of Custom Metric Autoscaler operator for Red Hat Openshift
- deployment-validation-operator-container as a component of Deployment Validation Operator
- rhoai/odh-data-science-pipelines-argo-argoexec-rhel8 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-data-science-pipelines-argo-workflowcontroller-rhel8 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-ml-pipelines-api-server-v2-rhel8 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-ml-pipelines-driver-rhel8 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-ml-pipelines-launcher-rhel8 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-ml-pipelines-persistenceagent-v2-rhel8 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-ml-pipelines-scheduledworkflow-v2-rhel8 as a component of Red Hat OpenShift AI (RHOAI)
- rhosdt/opentelemetry-operator-bundle as a component of Red Hat OpenShift distributed tracing 3
- rhosdt/opentelemetry-target-allocator-rhel8 as a component of Red Hat OpenShift distributed tracing 3
- rhosdt/tempo-rhel8-operator as a component of Red Hat OpenShift distributed tracing 3
- Fixed
- openshift-gitops-1/argo-rollouts-rhel8@sha256:1c3014b6fed55efec858979b8e716025b3c930ce73ce03376d6b344cc799f408_amd64 as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/argo-rollouts-rhel8@sha256:c0b31a9043e01767c4305bf53852e4e956a75bbf0d338e9bdd84693d854aadb1_arm64 as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/argo-rollouts-rhel8@sha256:cffc1a5602bc8275c83aff3a8397dc812b925494deb8105bad675e1eebc1ce4f_ppc64le as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/argo-rollouts-rhel8@sha256:f1551e8646b6f845566aa3786194b2cb3392240617ec33a8598e1361a2f7cf6e_s390x as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/argocd-extensions-rhel8@sha256:2959776572015171fe9e674bef16cd27207ad0dd9778597f61c92bd0b68419cb_arm64 as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/argocd-extensions-rhel8@sha256:6751efa0700ce5aca7e998b507f2694d36671c800bd3df39c1793fdb79295b01_s390x as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/argocd-extensions-rhel8@sha256:7de02503f35ffa0385273117b00104f7cd13cf62e90236a539b00d0a26914fe5_amd64 as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/argocd-extensions-rhel8@sha256:9628abc742fa7d3e4e7f76c42f86f729a12064b31c6fdcd4d56fd12de42c312d_ppc64le as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/argocd-rhel8@sha256:2b613ea76cf38f82b81c0f94bc1310f8221ebfae30e11bb3eb9a9322f7de781c_amd64 as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/argocd-rhel8@sha256:9b2b128beada3283376cb1e0daa09f3074e865cd13feff7e5cf4be22b80b73eb_arm64 as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/argocd-rhel8@sha256:adff90e820d35b5f6edb54e8a3e66a1944b3df7949b82b52757542990532a927_ppc64le as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/argocd-rhel8@sha256:c828786304a861504124f4adcef108a8ec2fbb1ffe39c6f40cbcd45421d9da63_s390x as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/console-plugin-rhel8@sha256:23d6aff07ace832a252e24f8c4f50fa7bb8071195266ca2ee1ecb85d2c8cd040_arm64 as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/console-plugin-rhel8@sha256:7cf81305f51be21dd5044cf2b5e252c3504a5593b25c79efd14ac4c07b845e0e_ppc64le as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/console-plugin-rhel8@sha256:b7729386eafdea2376dd9b95e2f30904f0a737108fa01643425a26817b2d49e3_s390x as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/console-plugin-rhel8@sha256:bd66924e532f909e4efe16a7d02556ce50d3aeb399a1c576365c58e28b217156_amd64 as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/dex-rhel8@sha256:3763f158afee4709f908f9069cafc53e6e19932a89206e1b1c161b83978c8bf3_ppc64le as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/dex-rhel8@sha256:4f556b4a5eb754b8310db23d78984612ce6fb1537a96cf5bba1ca4d9db24c458_s390x as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/dex-rhel8@sha256:5322e7c5c3e6648cbc31aef26c793fe446de59f926c9e420e7bbe69be5b7628c_amd64 as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/dex-rhel8@sha256:575fe0d90e61cd644293c9775b0b6670b159bf0e004b1514f65473a353ed157e_arm64 as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/gitops-operator-bundle@sha256:9233f5165c36e049c07f6c86bc4a330e8cd5c92fdb9e26364f83156e5079a573_amd64 as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/gitops-rhel8-operator@sha256:1ec8b3afca8969bb43413de847e9e42e863a00e618b2d75585a297f605d4c2cd_amd64 as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/gitops-rhel8-operator@sha256:b5bad8e3002354e708978aa81d8fb12ce244336677dd4b43d05a2e3d28ee21fe_arm64 as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/gitops-rhel8-operator@sha256:c11750919f393a494bd39f5430dd64502fda211e1e58b82b12b25c0aefb01b10_ppc64le as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/gitops-rhel8-operator@sha256:f44ea91f40a80ea0ceb8ce162344632fa4ac83a25e40e3e268a04960dd4cef8e_s390x as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/gitops-rhel8@sha256:02615dcef407b4c180d2136fd2d0179b75a938663530173c3155fc137158b9ef_ppc64le as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/gitops-rhel8@sha256:2fdc37ff27fe77bcf1b49b5067cc29250ec8e1073a1e3d747c46471a12a23bd2_s390x as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/gitops-rhel8@sha256:bab70614afc93dde060a53ae72f677c979851881160f434a7b3a82c208122222_amd64 as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/gitops-rhel8@sha256:bfd4fc073330dff519a73394fd300f304dce3b7d4de1cc741324af08085819e6_arm64 as a component of Red Hat OpenShift GitOps 1.15
- openshift-gitops-1/must-gather-rhel8@sha256:a19ac137261209f8d9a0648179637ea7c2a4e0e605c6f1370de6f74deea62676_arm64 as a component of Red Hat OpenShift GitOps 1.15
- and 41 more
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 17 Mar 2025 · Last source change 23 Jan 2026, 16:29 UTC · CWE-770 · Allocation of Resources Without Limits or Throttling
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2025-6527
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- < 1.17.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- < 1.17.0 · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
- Remediation statusRemediation status changed from Awaiting fix to Patch available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Patch available
CVE published
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.