# 24 terms a reader meets, each with a sourced example

Glossary, read 19 Nov 2026

**The short answer.** The glossary defines 24 terms used in exploitability work, from attack path and call graph to precondition and reachability. Standard terms quote NIST, FIRST, CISA, MITRE or the CVE Program; vendor descriptions are labelled as vendor claims and the site's own definitions as such. Each term adds a dated example from the 37 ledger CVEs.

- [Agent investigation](#agent-investigation)
- [Attack path](#attack-path)
- [Attack vector](#attack-vector)
- [Call graph](#call-graph)
- [CVE](#cve)
- [CVSS base score](#cvss-base)
- [CWE](#cwe)
- [Disclosure date](#disclosure-date)
- [EPSS](#epss)
- [Exploitability](#exploitability)
- [Exploitation in the wild](#exploited-in-the-wild)
- [Forensic triage](#forensic-triage)
- [Indicator of compromise](#indicator-of-compromise)
- [Known Exploited Vulnerabilities catalog](#kev)
- [National Vulnerability Database](#nvd)
- [Precondition](#precondition)
- [Privileges required](#privileges-required)
- [Proof of concept](#proof-of-concept)
- [Reachability](#reachability)
- [Runtime reachability](#runtime-reachability)
- [Static reachability](#static-reachability)
- [Transitive dependency](#transitive-dependency)
- [Vulnerable](#vulnerable)
- [Zero-day](#zero-day)

## Agent investigation

No standards body defines agent investigation. Onit's documentation, a vendor claim, describes a Reachability Agent that "reads the network path an attacker would take, from the internet edge inward, and marks each exposure Reachable, Not Reachable or Unknown" ([Onit](https://onit.security/blog/ai-agents-vulnerability-management/)). On this site the term is the site's own: an automated reader that works one finding at a time and leaves a record of the evidence it used and what it could not settle.

Example: CVE-2026-82329 in JFrog Artifactory is exploitable only on a default install where no additionalJoinKeys value is set and the Access service join endpoint is reachable, so an agent checks that setting, the exposure and tokens issued since the 28 Aug 2026 disclosure. See [the ledger entry](/ledger/cve-2026-82329/). ([source](https://docs.jfrog.com/releases/docs/jfrog-security-advisories), read 19 Nov 2026)

## Attack path

Microsoft's Defender for Cloud documentation, a vendor description of its own feature, says it "uses a proprietary algorithm to locate potential attack paths in your multicloud environment", and that these are paths that "start outside your organization and lead to critical targets" ([Microsoft Learn](https://learn.microsoft.com/en-us/azure/defender-for-cloud/how-to-manage-attack-path)). The site's own definition: an attack path joins reachability, privilege and controls into one route from an attacker's position to an asset.

Example: CVE-2026-76460 in Cisco ISE, rated 10.0 and listed in KEV on 16 Sep 2026, turns on whether an attacker can reach the ISE API from a foothold, which is why Cisco's mitigation is access control lists. See [the ledger entry](/ledger/cve-2026-76460/). ([source](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ISE-ABP-VNSW7Tn5), read 19 Nov 2026)

## Attack vector

FIRST defines the CVSS Attack Vector metric as reflecting "the context by which vulnerability exploitation is possible", with the values network, adjacent, local and physical. The more remote the attacker can be, the higher the rating. Of the 37 ledger CVEs, 31 carry a network vector and 6 a local one.

Example: CVE-2026-81963 in the Windows Update Stack carries AV:L and PR:L, so exploitation needs a low-privileged local session that already exists, and the 8 Sep 2026 cumulative updates fix it. See [the ledger entry](/ledger/cve-2026-81963/). (sources for the example: [NVD record for CVE-2026-81963](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-81963), [Microsoft CVRF for September 2026](https://api.msrc.microsoft.com/cvrf/v3.0/cvrf/2026-Sep), read 19 Nov 2026; [source for the definition](https://www.first.org/cvss/v4.0/specification-document), read 19 Nov 2026)

## Call graph

Endor Labs, a vendor, describes its call graph analysis as a way to mitigate open source vulnerabilities by "pinpointing and understanding the invocation of vulnerable methods". A call graph maps which function calls which, so a tool can test whether any path from application code reaches the vulnerable function inside a dependency.

Example: CVE-2026-16723 in fastjson 1.2.68 to 1.2.83 matters in a service only when a call path parses attacker-supplied JSON; the fix is fastjson 1.2.84, released 29 Jul 2026. See [the ledger entry](/ledger/cve-2026-16723/). ([source for the example](https://github.com/alibaba/fastjson/releases/tag/1.2.84), read 19 Nov 2026; [source for the definition](https://docs.endorlabs.com/scan/sca/call-graphs/index), read 19 Nov 2026)

## CVE

The mission of the CVE Program, in its own words, is "to identify, define, and catalog publicly disclosed cybersecurity vulnerabilities". A CVE identifier names one flaw so that advisories, NVD and the KEV catalog can refer to the same thing. The identifier says nothing about severity, exposure or whether the flaw is exploited.

Example: CVE-2026-111497 names the Brotli decoder out-of-bounds write that affects Node.js 22.x, 24.x and 26.x before the fixed releases, and any software embedding Brotli from 1.0.3 up to but excluding 1.0.10, 1.1.0 up to 1.1.1 and 1.2.0 up to 1.2.1. See [the ledger entry](/ledger/cve-2026-111497/). (sources for the example: [Node.js security releases of 21 Oct 2026](https://nodejs.org/en/blog/vulnerability/october-2026-security-releases), [Brotli 1.2.1 release notes](https://github.com/google/brotli/releases/tag/v1.2.1), [NVD record for CVE-2026-111497](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-111497), read 19 Nov 2026; [source for the definition](https://cve.mitre.org/), read 19 Nov 2026)

## CVSS base score

FIRST states that the CVSS Base group "represents the intrinsic qualities of a vulnerability that are constant over time and across user environments". A base score therefore rates the flaw, not your system: it ignores whether the feature is on, the port is open or exploitation has been seen.

Example: Broadcom rates CVE-2026-41709 in VMware ESX at 2.7, with high privileges required, and CISA still added it to KEV on 28 Oct 2026, 91 days after the 29 Jul 2026 disclosure. See [the ledger entry](/ledger/cve-2026-41709/). (sources for the example: [Broadcom advisory VMSA-2026-0006](https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017), [CISA KEV feed 2026.11.18](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json), read 19 Nov 2026; [source for the definition](https://www.first.org/cvss/v4.0/specification-document), read 19 Nov 2026)

## CWE

MITRE describes CWE as "a community-developed list of common software and hardware weaknesses", where a weakness is "a condition in a software, firmware, hardware, or service component that, under certain circumstances, could contribute to the introduction of vulnerabilities". A CWE names the type of flaw, not the instance.

Example: CVE-2026-109618 in PHP is CWE-416, use after free, in PHP 8.2 before 8.2.35, 8.3 before 8.3.36, 8.4 before 8.4.27 and 8.5 before 8.5.12. See [the ledger entry](/ledger/cve-2026-109618/). (sources for the example: [PHP advisory GHSA-w8hw-w9fx-j79w](https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w), [NVD record for CVE-2026-109618](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-109618), read 19 Nov 2026; [source for the definition](https://cwe.mitre.org/about/index.html), read 19 Nov 2026)

## Disclosure date

Disclosure date is the site's own term: the day a vendor advisory or a CVE record first made the flaw public, whichever the ledger can date. Days from disclosure to first exploitation are counted from it, and a negative count means exploitation came first.

Example: BeyondTrust disclosed CVE-2026-102764 on 15 Oct 2026 and reports exploitation from 29 Aug 2026, a gap of minus 47 days. Ten of the 33 were exploited on the disclosure day and two before it. See [the ledger entry](/ledger/cve-2026-102764/). ([source](https://www.beyondtrust.com/blog/entry/bt26-05), read 19 Nov 2026)

## EPSS

FIRST states that "EPSS (Exploit Prediction Scoring System) is a data-driven model that estimates the probability a vulnerability will be exploited in the wild within the next 30 days", as a value between 0 and 1 for every CVE. It is a population-level estimate and not a measure of damage or of one environment.

Example: FIRST's FAQ adds that "EPSS scores reflect exploitation probability across the global observed population, not your specific environment". On 18 Nov 2026 the EPSS API gave CVE-2026-76460 in Cisco ISE a probability of 0.756 (percentile 0.995) and CVE-2026-41709 in VMware ESX 0.0069 (percentile 0.535); both are in KEV, and ESX carries a CVSS base score of 2.7 ([FIRST EPSS API](https://api.first.org/data/v1/epss?cve=CVE-2026-41709,CVE-2026-76460), read 19 Nov 2026). None of the 37 ledger CVEs settles on an EPSS value alone. See [the ledger entry](/ledger/cve-2026-41709/). ([source](https://www.first.org/epss/faq), read 19 Nov 2026)

## Exploitability

Exploitability, as the site defines it (no standard text applies): whether a flaw can be used against one specific system on one date, given its version, configuration, exposure and the attacker's starting access. The judgment belongs to an environment and is not a property of the CVE. A ledger entry lists every condition from the advisory that must hold at once.

Example: CVE-2026-0322 in PAN-OS needs a build below the fixed build for its train, network reach to the management interface and a high-privilege account; the advisory is dated 14 Oct 2026. See [the ledger entry](/ledger/cve-2026-0322/). ([source](https://security.paloaltonetworks.com/CVE-2026-0322), read 19 Nov 2026)

## Exploitation in the wild

CISA's KEV page defines a vulnerability under active exploitation as "one for which there is reliable evidence that execution of malicious code was performed by an actor on a system without permission of the system owner", and says this includes attempted as well as successful exploitation. A vendor advisory may report exploitation earlier or later than the catalog does.

Example: Fortinet advisory FG-IR-26-175, published 1 Oct 2026, says CVE-2026-104286 "has been reported to be exploited in the wild", and CISA listed it the same day. See [the ledger entry](/ledger/cve-2026-104286/). ([source for the example](https://fortiguard.fortinet.com/psirt/FG-IR-26-175), read 19 Nov 2026; [source for the definition](https://www.cisa.gov/known-exploited-vulnerabilities), read 19 Nov 2026)

## Forensic triage

CISA's BOD 26-04 says forensic triage means that the agency must "complete remediation or mitigation action within the timeline (three days)" and also triage the asset "to assess whether the system is compromised". Patching alone does not show whether an attacker was already inside.

Example: In KEV feed 2026.11.18, 19 of the 33 ledger CVEs carry the forensic triage flag, among them CVE-2026-0322 and CVE-2026-76460, while CVE-2026-41709 does not. See [the ledger entry](/ledger/cve-2026-76460/). (sources for the example: [CISA KEV feed 2026.11.18](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json), read 19 Nov 2026; [source for the definition](https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk), read 19 Nov 2026)

## Indicator of compromise

NIST's glossary defines indicators of compromise as "Technical artifacts or observables that suggest that an attack is imminent or is currently underway or that a compromise may have already occurred". Checking for them after patching shows whether someone got in before the fix.

Example: Fortinet lists two indicator addresses, 79[.]141[.]169[.]187 and 45[.]129[.]0[.]192, and system event log lines for CVE-2026-104286 in FG-IR-26-175. See [the ledger entry](/ledger/cve-2026-104286/). ([source for the example](https://fortiguard.fortinet.com/psirt/FG-IR-26-175), read 19 Nov 2026; [source for the definition](https://csrc.nist.gov/glossary/term/indicator_of_compromise), read 19 Nov 2026)

## Known Exploited Vulnerabilities catalog

CISA's KEV catalog page says CISA "maintains the authoritative source of vulnerabilities that have been exploited in the wild". An entry shows that exploitation was observed somewhere, not that every installation is exposed. Each entry carries a due date, a ransomware flag and, under BOD 26-04, a forensic triage flag.

Example: The JSON feed of version 2026.11.18, read on 19 Nov 2026, held 1,786 entries, and 33 of the 37 ledger CVEs are in it, matched by CVE ID. CVE-2026-76418 in Cisco ASA and FTD was added on 29 Oct 2026. See [the ledger entry](/ledger/cve-2026-76418/). (sources for the example: [CISA KEV feed 2026.11.18](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json), read 19 Nov 2026; [source for the definition](https://www.cisa.gov/known-exploited-vulnerabilities-catalog), read 19 Nov 2026)

## National Vulnerability Database

The National Vulnerability Database, run by NIST, publishes each CVE record with a CVSS rating, a weakness type and affected-product ranges expressed as CPE data. Its version ranges can differ from the vendor's table, so a ledger record gives the vendor's table where the two disagree and says so.

Example: The NVD record for CVE-2026-46300 lists Linux 3.9 through 5.10.257 as affected, but no 5.10 stable release from 5.10.258 to 5.10.274 contains the fix, which the ledger record states. See [the ledger entry](/ledger/cve-2026-46300/). ([source](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-46300), read 19 Nov 2026)

## Precondition

Precondition is the site's own term: a condition in an advisory that must hold before a flaw can be exploited, such as a version, an enabled feature, a reachable interface or an attacker privilege. A finding is exploitable on a system only when all of its preconditions hold. Ledger entries list preconditions before the fix.

Example: CVE-2026-123158 needs sshd built against musl libc without PAM, password authentication on, a reachable port, and an account with a * password field whose name the attacker knows. OpenSSH 10.6p2 shipped on 5 Nov 2026. See [the ledger entry](/ledger/cve-2026-123158/). ([source](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-123158), read 19 Nov 2026)

## Privileges required

FIRST says this metric "describes the level of privileges an attacker must possess prior to successfully exploiting the vulnerability", with the values none, low and high. Across the 37 ledger CVEs, 25 need none, 10 need low privileges and 2 need high privileges.

Example: CVE-2026-0322 in PAN-OS and CVE-2026-41709 in VMware ESX are the two entries with PR:H, which means an administrator account on the management interface or host. See [the ledger entry](/ledger/cve-2026-0322/). (sources for the example: [NVD record for CVE-2026-0322](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-0322), [NVD record for CVE-2026-41709](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-41709), read 19 Nov 2026; [source for the definition](https://www.first.org/cvss/v4.0/specification-document), read 19 Nov 2026)

## Proof of concept

CISA's KEV page defines proof of concept (PoC) as "the code for a vulnerability that, when executed, would allow for exploitation", and says that "making PoC publicly available can increase the likelihood of an attacker exploiting the vulnerability in the wild" but does not by itself show that the flaw has been or will be exploited. The ledger records that a proof of concept appeared, with its date, and never reproduces its steps.

Example: Fastly counted about 75,000 attempts against Artifactory CVE-2026-82329 on 31 Aug 2026, mostly offensive security services, and about 171,000 on 1 Sep 2026 after a public exploit appeared. See [the ledger entry](/ledger/cve-2026-82329/). ([source for the example](https://www.fastly.com/blog/cve-2026-82329-jfrog-artifactory-authentication-bypass-exploitation-activity), read 19 Nov 2026; [source for the definition](https://www.cisa.gov/known-exploited-vulnerabilities), read 19 Nov 2026)

## Reachability

The OpenVEX specification names the case that reachability analysis tests, the status justification vulnerable_code_not_in_execute_path: "Typically, this case occurs when the product includes the vulnerable subcomponent but does not call or use the vulnerable code". The question has two halves: is the code called, and can the service be reached from where an attacker stands.

Example: Snyk, a vendor, says its reachability analysis works by "identifying whether your application is calling a code element (for example, functions, classes, modules, and more) related to the vulnerability", and notes that "it is not always possible to give a precise answer when reflection programming is used", so no path found is weaker than path ruled out. CVE-2026-111497 is reachable only where a service decompresses Brotli data an attacker can influence. See [the ledger entry](/ledger/cve-2026-111497/). ([source for the example](https://docs.snyk.io/manage-risk/prioritize-issues-for-fixing/reachability-analysis), read 19 Nov 2026; [source for the definition](https://github.com/openvex/spec/blob/main/OPENVEX-SPEC.md), read 19 Nov 2026)

## Runtime reachability

Endor Labs, a vendor, describes instrumented container reachability as embedding "a runtime sensor in your container image to record how your application uses the image in a real environment". Runtime reachability observes calls while a workload runs, so it proves a call happened and says nothing about paths the observation window never exercised.

Example: CVE-2026-46300 in the Linux kernel is settled on the running host: whether esp4 or esp6 is loaded and whether unprivileged user namespaces are allowed. The stable kernel releases carrying the fix shipped on 23 May 2026. See [the ledger entry](/ledger/cve-2026-46300/). ([source for the example](https://access.redhat.com/security/cve/CVE-2026-46300), read 19 Nov 2026; [source for the definition](https://docs.endorlabs.com/scan/containers/instrumented-reachability/index), read 19 Nov 2026)

## Static reachability

Static reachability is the site's own term; no standard text defines it. It reads code or configuration without running it, and asks whether a path runs from an entry point to the vulnerable element or whether the affected version and setting are present. A found path shows exposure is possible. A missing path is weaker evidence, because reflection and dynamic loading hide calls.

Example: CVE-2026-94545 affects Satori and next/og only on the Node.js runtime and only when attacker-controlled values reach SVG content, attributes or styles; a source search decides it, and Next.js 16.3.6 fixes it. See [the ledger entry](/ledger/cve-2026-94545/). ([source](https://github.com/vercel/next.js/security/advisories/GHSA-vcvr-r3jv-pc5j), read 19 Nov 2026)

## Transitive dependency

The Apache Maven documentation says Maven "avoids the need to discover and specify the libraries that your own dependencies require by including transitive dependencies automatically". A scanner can flag a flaw in a library the manifest never names, while the call site sits two levels down. The resolved version in the build output, not the manifest, shows which version is present.

Example: CVE-2026-16723 affects fastjson 1.2.68 to 1.2.83 and is fixed in 1.2.84. A Maven project that never lists com.alibaba:fastjson in its pom.xml still carries it when another dependency requires it, and mvn dependency:tree shows the resolved version. See [the ledger entry](/ledger/cve-2026-16723/). ([source for the example](https://github.com/alibaba/fastjson/releases/tag/1.2.84), read 19 Nov 2026; [source for the definition](https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html), read 19 Nov 2026)

## Vulnerable

NIST's glossary defines a vulnerability as a "Weakness in an information system, system security procedures, internal controls, or implementation that could be exploited or triggered by a threat source." A system is vulnerable when it runs affected code, which says nothing yet about whether an attacker can reach it.

Example: CVE-2026-75604 affects Next.js 13.4.0 before 15.5.24 and 16.0.0 before 16.3.3, but the NVD record names a Windows filesystem as a condition. A Linux host running 15.5.20 falls inside the version ranges, so a scanner flags it, yet the record's Windows condition does not hold there. A version match alone does not settle it. See [the ledger entry](/ledger/cve-2026-75604/). ([source for the example](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-75604), read 19 Nov 2026; [source for the definition](https://csrc.nist.gov/glossary/term/vulnerability), read 19 Nov 2026)

## Zero-day

NIST's glossary, quoting CNSSI 4009-2022, defines a zero-day attack as "An attack that exploits a previously unknown hardware, firmware, or software vulnerability." In the ledger, exploitation dated before the disclosure date marks a zero-day, and two entries meet that test.

Example: CVE-2026-75650 in Adobe Commerce was exploited from 4 Sep 2026, three days before Adobe's bulletin of 7 Sep 2026. CVE-2026-102764 in BeyondTrust was exploited 47 days before disclosure. See [the ledger entry](/ledger/cve-2026-75650/). (sources for the example: [Sansec research](https://sansec.io/research/stylesmuggler-0day), [BeyondTrust bulletin BT26-05](https://www.beyondtrust.com/blog/entry/bt26-05), read 19 Nov 2026; [source for the definition](https://csrc.nist.gov/glossary/term/zero_day_attack), read 19 Nov 2026)

## Related pages

- [Exploitability Ledger: the data, downloadable](/datasets/)
- [The Methods Matrix](/matrix/)

## Sources

- https://docs.jfrog.com/releases/docs/jfrog-security-advisories (read 19 Nov 2026)
- https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ISE-ABP-VNSW7Tn5 (read 19 Nov 2026)
- https://www.first.org/cvss/v4.0/specification-document (read 19 Nov 2026)
- https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-81963 (read 19 Nov 2026)
- https://api.msrc.microsoft.com/cvrf/v3.0/cvrf/2026-Sep (read 19 Nov 2026)
- https://docs.endorlabs.com/scan/sca/call-graphs/index (read 19 Nov 2026)
- https://github.com/alibaba/fastjson/releases/tag/1.2.84 (read 19 Nov 2026)
- https://cve.mitre.org/ (read 19 Nov 2026)
- https://nodejs.org/en/blog/vulnerability/october-2026-security-releases (read 19 Nov 2026)
- https://github.com/google/brotli/releases/tag/v1.2.1 (read 19 Nov 2026)
- https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-111497 (read 19 Nov 2026)
- https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017 (read 19 Nov 2026)
- https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json (read 19 Nov 2026)
- https://cwe.mitre.org/about/index.html (read 19 Nov 2026)
- https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w (read 19 Nov 2026)
- https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-109618 (read 19 Nov 2026)
- https://www.beyondtrust.com/blog/entry/bt26-05 (read 19 Nov 2026)
- https://www.first.org/epss/faq (read 19 Nov 2026)
- https://security.paloaltonetworks.com/CVE-2026-0322 (read 19 Nov 2026)
- https://www.cisa.gov/known-exploited-vulnerabilities (read 19 Nov 2026)
- https://fortiguard.fortinet.com/psirt/FG-IR-26-175 (read 19 Nov 2026)
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk (read 19 Nov 2026)
- https://csrc.nist.gov/glossary/term/indicator_of_compromise (read 19 Nov 2026)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog (read 19 Nov 2026)
- https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-46300 (read 19 Nov 2026)
- https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-123158 (read 19 Nov 2026)
- https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-0322 (read 19 Nov 2026)
- https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-41709 (read 19 Nov 2026)
- https://www.fastly.com/blog/cve-2026-82329-jfrog-artifactory-authentication-bypass-exploitation-activity (read 19 Nov 2026)
- https://github.com/openvex/spec/blob/main/OPENVEX-SPEC.md (read 19 Nov 2026)
- https://docs.snyk.io/manage-risk/prioritize-issues-for-fixing/reachability-analysis (read 19 Nov 2026)
- https://docs.endorlabs.com/scan/containers/instrumented-reachability/index (read 19 Nov 2026)
- https://access.redhat.com/security/cve/CVE-2026-46300 (read 19 Nov 2026)
- https://github.com/vercel/next.js/security/advisories/GHSA-vcvr-r3jv-pc5j (read 19 Nov 2026)
- https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html (read 19 Nov 2026)
- https://csrc.nist.gov/glossary/term/vulnerability (read 19 Nov 2026)
- https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-75604 (read 19 Nov 2026)
- https://csrc.nist.gov/glossary/term/zero_day_attack (read 19 Nov 2026)
- https://sansec.io/research/stylesmuggler-0day (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://reachabilityanalysis.com/glossary/
