CVE-2026-114214 (GCVE-0-2026-114214)
Vulnerability from cvelistv5
Published
2026-10-25 19:47
Modified
2026-10-26 14:35
Severity ?
VLAI Severity ?
EPSS score ?
CWE
- CWE-863 - Incorrect Authorization
Summary
Incorrect Authorization vulnerability in ash-project ash allows a client to read destination records unrelated to the source record through a through relationship.
When a has_many relationship declared with through: was loaded for a single record with a limit of 1, or an unsorted has_one through relationship was loaded with a limit of 1, lateral_join?/4 in lib/ash/actions/read/relationships.ex chose the path that reads the destination without any filter linking it to the source. The load returned the first destination record by sort, or any other record with an offset. The read still runs the destination's policies but carries the relationship as accessing_from, so a client paging such a field (for example teachers(limit: 1, offset: n) through AshGraphql) can enumerate destination records that policies allow only when reached through that relationship.
This issue affects ash: from 3.24.0 before 3.37.1.
References
Impacted products
| Vendor | Product | Version | |||||||
|---|---|---|---|---|---|---|---|---|---|
| ash-project | ash |
Version: 3.24.0 ≤ cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:* |
|||||||
|
|||||||||
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-114214",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-26T14:28:34.411522Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-10-26T14:35:21.414Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://repo.hex.pm",
"cpes": [
"cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"\u0027Elixir.Ash.Actions.Read.Relationships\u0027"
],
"packageName": "ash",
"packageURL": "pkg:hex/ash",
"product": "ash",
"programFiles": [
"lib/ash/actions/read/relationships.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.Ash.Actions.Read.Relationships\u0027:lateral_join?/4"
},
{
"name": "\u0027Elixir.Ash.Actions.Read.Relationships\u0027:load/4"
}
],
"repo": "https://github.com/ash-project/ash",
"vendor": "ash-project",
"versions": [
{
"lessThan": "3.37.1",
"status": "affected",
"version": "3.24.0",
"versionType": "semver"
}
]
},
{
"collectionURL": "https://github.com",
"cpes": [
"cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"\u0027Elixir.Ash.Actions.Read.Relationships\u0027"
],
"packageName": "ash-project/ash",
"packageURL": "pkg:github/ash-project/ash",
"product": "ash",
"programFiles": [
"lib/ash/actions/read/relationships.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.Ash.Actions.Read.Relationships\u0027:lateral_join?/4"
},
{
"name": "\u0027Elixir.Ash.Actions.Read.Relationships\u0027:load/4"
}
],
"repo": "https://github.com/ash-project/ash",
"vendor": "ash-project",
"versions": [
{
"lessThan": "e37463307304b26bc8fd606322e5c4d8f7f060e5",
"status": "affected",
"version": "24f41e23dcbd9d07cde270a8141490e8f79251f5",
"versionType": "git"
}
]
}
],
"configurations": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eReachable when a \u003ccode\u003ethrough\u003c/code\u003e relationship is loaded for a single record with a caller-controlled limit of 1 (and optionally an offset), for example through AshGraphql relationship field arguments, and the destination resource\u0027s read policies rely on the relationship (\u003ccode\u003eaccessing_from\u003c/code\u003e) or are otherwise open to the caller.\u003c/p\u003e"
},
{
"base64": false,
"type": "text/markdown",
"value": "Reachable when a `through` relationship is loaded for a single record with a caller-controlled limit of 1 (and optionally an offset), for example through AshGraphql relationship field arguments, and the destination resource\u0027s read policies rely on the relationship (`accessing_from`) or are otherwise open to the caller."
}
],
"value": "Reachable when a through relationship is loaded for a single record with a caller-controlled limit of 1 (and optionally an offset), for example through AshGraphql relationship field arguments, and the destination resource\u0027s read policies rely on the relationship (accessing_from) or are otherwise open to the caller."
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:*",
"versionEndExcluding": "3.37.1",
"versionStartIncluding": "3.24.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "AND"
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Will Townsend"
},
{
"lang": "en",
"type": "reporter",
"value": "Will Townsend"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Zach Daniel / Ash Project"
}
],
"dateAssigned": "2026-10-25T17:24:26.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eIncorrect Authorization vulnerability in ash-project ash allows a client to read destination records unrelated to the source record through a \u003ccode\u003ethrough\u003c/code\u003e relationship.\u003c/p\u003e\n\u003cp\u003eWhen a \u003ccode\u003ehas_many\u003c/code\u003e relationship declared with \u003ccode\u003ethrough:\u003c/code\u003e was loaded for a single record with a limit of 1, or an unsorted \u003ccode\u003ehas_one\u003c/code\u003e \u003ccode\u003ethrough\u003c/code\u003e relationship was loaded with a limit of 1, \u003ccode\u003elateral_join?/4\u003c/code\u003e in \u003ccode\u003elib/ash/actions/read/relationships.ex\u003c/code\u003e chose the path that reads the destination without any filter linking it to the source. The load returned the first destination record by sort, or any other record with an \u003ccode\u003eoffset\u003c/code\u003e. The read still runs the destination\u0027s policies but carries the relationship as \u003ccode\u003eaccessing_from\u003c/code\u003e, so a client paging such a field (for example \u003ccode\u003eteachers(limit: 1, offset: n)\u003c/code\u003e through AshGraphql) can enumerate destination records that policies allow only when reached through that relationship.\u003c/p\u003e\n\u003cp\u003eThis issue affects ash: from 3.24.0 before 3.37.1.\u003c/p\u003e"
},
{
"base64": false,
"type": "text/markdown",
"value": "Incorrect Authorization vulnerability in ash-project ash allows a client to read destination records unrelated to the source record through a `through` relationship.\n\nWhen a `has_many` relationship declared with `through:` was loaded for a single record with a limit of 1, or an unsorted `has_one` `through` relationship was loaded with a limit of 1, `lateral_join?/4` in `lib/ash/actions/read/relationships.ex` chose the path that reads the destination without any filter linking it to the source. The load returned the first destination record by sort, or any other record with an `offset`. The read still runs the destination\u0027s policies but carries the relationship as `accessing_from`, so a client paging such a field (for example `teachers(limit: 1, offset: n)` through AshGraphql) can enumerate destination records that policies allow only when reached through that relationship.\n\nThis issue affects ash: from 3.24.0 before 3.37.1."
}
],
"value": "Incorrect Authorization vulnerability in ash-project ash allows a client to read destination records unrelated to the source record through a through relationship.\n\nWhen a has_many relationship declared with through: was loaded for a single record with a limit of 1, or an unsorted has_one through relationship was loaded with a limit of 1, lateral_join?/4 in lib/ash/actions/read/relationships.ex chose the path that reads the destination without any filter linking it to the source. The load returned the first destination record by sort, or any other record with an offset. The read still runs the destination\u0027s policies but carries the relationship as accessing_from, so a client paging such a field (for example teachers(limit: 1, offset: n) through AshGraphql) can enumerate destination records that policies allow only when reached through that relationship.\n\nThis issue affects ash: from 3.24.0 before 3.37.1."
}
],
"impacts": [
{
"capecId": "CAPEC-1",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eA client paging a through relationship field with a limit of 1 reads destination records that should only be reachable through that relationship.\u003c/p\u003e"
},
{
"base64": false,
"type": "text/markdown",
"value": "A client paging a through relationship field with a limit of 1 reads destination records that should only be reachable through that relationship."
}
],
"value": "A client paging a through relationship field with a limit of 1 reads destination records that should only be reachable through that relationship."
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 6,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-863",
"description": "CWE-863 Incorrect Authorization",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-25T19:47:30.612Z",
"orgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"shortName": "EEF"
},
"references": [
{
"name": "Loading a `through` relationship on a single record with `limit: 1` ignores the through path and returns arbitrary destination records",
"tags": [
"vendor-advisory",
"related"
],
"url": "https://github.com/ash-project/ash/security/advisories/GHSA-g2h4-xp57-q863"
},
{
"name": "EEF CNA record for CVE-2026-114214",
"tags": [
"related"
],
"url": "https://cna.erlef.org/cves/CVE-2026-114214.html"
},
{
"name": "OSV record EEF-CVE-2026-114214",
"tags": [
"related"
],
"url": "https://osv.dev/vulnerability/EEF-CVE-2026-114214"
},
{
"name": "Introducing commit 24f41e2 in ash-project/ash",
"tags": [
"related"
],
"url": "https://github.com/ash-project/ash/commit/24f41e23dcbd9d07cde270a8141490e8f79251f5"
},
{
"name": "Fix commit e374633 in ash-project/ash",
"tags": [
"patch"
],
"url": "https://github.com/ash-project/ash/commit/e37463307304b26bc8fd606322e5c4d8f7f060e5"
}
],
"source": {
"discovery": "EXTERNAL"
},
"title": "Loading a through relationship with a limit of 1 in Ash ignores the through path and returns unrelated destination records"
}
},
"cveMetadata": {
"assignerOrgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"assignerShortName": "EEF",
"cveId": "CVE-2026-114214",
"datePublished": "2026-10-25T19:47:30.612Z",
"dateReserved": "2026-10-25T14:30:01.870Z",
"dateUpdated": "2026-10-26T14:35:21.414Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"vulnrichment": {
"containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-114214\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-10-26T14:28:34.411522Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-10-26T14:32:22.023Z\"}}], \"cna\": {\"title\": \"Loading a through relationship with a limit of 1 in Ash ignores the through path and returns unrelated destination records\", \"source\": {\"discovery\": \"EXTERNAL\"}, \"credits\": [{\"lang\": \"en\", \"type\": \"finder\", \"value\": \"Will Townsend\"}, {\"lang\": \"en\", \"type\": \"reporter\", \"value\": \"Will Townsend\"}, {\"lang\": \"en\", \"type\": \"remediation developer\", \"value\": \"Zach Daniel / Ash Project\"}], \"impacts\": [{\"capecId\": \"CAPEC-1\", \"descriptions\": [{\"lang\": \"en\", \"value\": \"A client paging a through relationship field with a limit of 1 reads destination records that should only be reachable through that relationship.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eA client paging a through relationship field with a limit of 1 reads destination records that should only be reachable through that relationship.\u003c/p\u003e\", \"base64\": false}, {\"type\": \"text/markdown\", \"value\": \"A client paging a through relationship field with a limit of 1 reads destination records that should only be reachable through that relationship.\", \"base64\": false}]}]}], \"metrics\": [{\"format\": \"CVSS\", \"cvssV4_0\": {\"Safety\": \"NOT_DEFINED\", \"version\": \"4.0\", \"Recovery\": \"NOT_DEFINED\", \"baseScore\": 6, \"Automatable\": \"NOT_DEFINED\", \"attackVector\": \"NETWORK\", \"baseSeverity\": \"MEDIUM\", \"valueDensity\": \"NOT_DEFINED\", \"vectorString\": \"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N\", \"providerUrgency\": \"NOT_DEFINED\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"attackRequirements\": \"PRESENT\", \"privilegesRequired\": \"LOW\", \"subIntegrityImpact\": \"NONE\", \"vulnIntegrityImpact\": \"NONE\", \"subAvailabilityImpact\": \"NONE\", \"vulnAvailabilityImpact\": \"NONE\", \"subConfidentialityImpact\": \"NONE\", \"vulnConfidentialityImpact\": \"HIGH\", \"vulnerabilityResponseEffort\": \"NOT_DEFINED\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"cpes\": [\"cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:*\"], \"repo\": \"https://github.com/ash-project/ash\", \"vendor\": \"ash-project\", \"modules\": [\"\u0027Elixir.Ash.Actions.Read.Relationships\u0027\"], \"product\": \"ash\", \"versions\": [{\"status\": \"affected\", \"version\": \"3.24.0\", \"lessThan\": \"3.37.1\", \"versionType\": \"semver\"}], \"packageURL\": \"pkg:hex/ash\", \"packageName\": \"ash\", \"programFiles\": [\"lib/ash/actions/read/relationships.ex\"], \"collectionURL\": \"https://repo.hex.pm\", \"defaultStatus\": \"unaffected\", \"programRoutines\": [{\"name\": \"\u0027Elixir.Ash.Actions.Read.Relationships\u0027:lateral_join?/4\"}, {\"name\": \"\u0027Elixir.Ash.Actions.Read.Relationships\u0027:load/4\"}]}, {\"cpes\": [\"cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:*\"], \"repo\": \"https://github.com/ash-project/ash\", \"vendor\": \"ash-project\", \"modules\": [\"\u0027Elixir.Ash.Actions.Read.Relationships\u0027\"], \"product\": \"ash\", \"versions\": [{\"status\": \"affected\", \"version\": \"24f41e23dcbd9d07cde270a8141490e8f79251f5\", \"lessThan\": \"e37463307304b26bc8fd606322e5c4d8f7f060e5\", \"versionType\": \"git\"}], \"packageURL\": \"pkg:github/ash-project/ash\", \"packageName\": \"ash-project/ash\", \"programFiles\": [\"lib/ash/actions/read/relationships.ex\"], \"collectionURL\": \"https://github.com\", \"defaultStatus\": \"unaffected\", \"programRoutines\": [{\"name\": \"\u0027Elixir.Ash.Actions.Read.Relationships\u0027:lateral_join?/4\"}, {\"name\": \"\u0027Elixir.Ash.Actions.Read.Relationships\u0027:load/4\"}]}], \"references\": [{\"url\": \"https://github.com/ash-project/ash/security/advisories/GHSA-g2h4-xp57-q863\", \"name\": \"Loading a `through` relationship on a single record with `limit: 1` ignores the through path and returns arbitrary destination records\", \"tags\": [\"vendor-advisory\", \"related\"]}, {\"url\": \"https://cna.erlef.org/cves/CVE-2026-114214.html\", \"name\": \"EEF CNA record for CVE-2026-114214\", \"tags\": [\"related\"]}, {\"url\": \"https://osv.dev/vulnerability/EEF-CVE-2026-114214\", \"name\": \"OSV record EEF-CVE-2026-114214\", \"tags\": [\"related\"]}, {\"url\": \"https://github.com/ash-project/ash/commit/24f41e23dcbd9d07cde270a8141490e8f79251f5\", \"name\": \"Introducing commit 24f41e2 in ash-project/ash\", \"tags\": [\"related\"]}, {\"url\": \"https://github.com/ash-project/ash/commit/e37463307304b26bc8fd606322e5c4d8f7f060e5\", \"name\": \"Fix commit e374633 in ash-project/ash\", \"tags\": [\"patch\"]}], \"dateAssigned\": \"2026-10-25T17:24:26.000Z\", \"descriptions\": [{\"lang\": \"en\", \"value\": \"Incorrect Authorization vulnerability in ash-project ash allows a client to read destination records unrelated to the source record through a through relationship.\\n\\nWhen a has_many relationship declared with through: was loaded for a single record with a limit of 1, or an unsorted has_one through relationship was loaded with a limit of 1, lateral_join?/4 in lib/ash/actions/read/relationships.ex chose the path that reads the destination without any filter linking it to the source. The load returned the first destination record by sort, or any other record with an offset. The read still runs the destination\u0027s policies but carries the relationship as accessing_from, so a client paging such a field (for example teachers(limit: 1, offset: n) through AshGraphql) can enumerate destination records that policies allow only when reached through that relationship.\\n\\nThis issue affects ash: from 3.24.0 before 3.37.1.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eIncorrect Authorization vulnerability in ash-project ash allows a client to read destination records unrelated to the source record through a \u003ccode\u003ethrough\u003c/code\u003e relationship.\u003c/p\u003e\\n\u003cp\u003eWhen a \u003ccode\u003ehas_many\u003c/code\u003e relationship declared with \u003ccode\u003ethrough:\u003c/code\u003e was loaded for a single record with a limit of 1, or an unsorted \u003ccode\u003ehas_one\u003c/code\u003e \u003ccode\u003ethrough\u003c/code\u003e relationship was loaded with a limit of 1, \u003ccode\u003elateral_join?/4\u003c/code\u003e in \u003ccode\u003elib/ash/actions/read/relationships.ex\u003c/code\u003e chose the path that reads the destination without any filter linking it to the source. The load returned the first destination record by sort, or any other record with an \u003ccode\u003eoffset\u003c/code\u003e. The read still runs the destination\u0027s policies but carries the relationship as \u003ccode\u003eaccessing_from\u003c/code\u003e, so a client paging such a field (for example \u003ccode\u003eteachers(limit: 1, offset: n)\u003c/code\u003e through AshGraphql) can enumerate destination records that policies allow only when reached through that relationship.\u003c/p\u003e\\n\u003cp\u003eThis issue affects ash: from 3.24.0 before 3.37.1.\u003c/p\u003e\", \"base64\": false}, {\"type\": \"text/markdown\", \"value\": \"Incorrect Authorization vulnerability in ash-project ash allows a client to read destination records unrelated to the source record through a `through` relationship.\\n\\nWhen a `has_many` relationship declared with `through:` was loaded for a single record with a limit of 1, or an unsorted `has_one` `through` relationship was loaded with a limit of 1, `lateral_join?/4` in `lib/ash/actions/read/relationships.ex` chose the path that reads the destination without any filter linking it to the source. The load returned the first destination record by sort, or any other record with an `offset`. The read still runs the destination\u0027s policies but carries the relationship as `accessing_from`, so a client paging such a field (for example `teachers(limit: 1, offset: n)` through AshGraphql) can enumerate destination records that policies allow only when reached through that relationship.\\n\\nThis issue affects ash: from 3.24.0 before 3.37.1.\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-863\", \"description\": \"CWE-863 Incorrect Authorization\"}]}], \"configurations\": [{\"lang\": \"en\", \"value\": \"Reachable when a through relationship is loaded for a single record with a caller-controlled limit of 1 (and optionally an offset), for example through AshGraphql relationship field arguments, and the destination resource\u0027s read policies rely on the relationship (accessing_from) or are otherwise open to the caller.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eReachable when a \u003ccode\u003ethrough\u003c/code\u003e relationship is loaded for a single record with a caller-controlled limit of 1 (and optionally an offset), for example through AshGraphql relationship field arguments, and the destination resource\u0027s read policies rely on the relationship (\u003ccode\u003eaccessing_from\u003c/code\u003e) or are otherwise open to the caller.\u003c/p\u003e\", \"base64\": false}, {\"type\": \"text/markdown\", \"value\": \"Reachable when a `through` relationship is loaded for a single record with a caller-controlled limit of 1 (and optionally an offset), for example through AshGraphql relationship field arguments, and the destination resource\u0027s read policies rely on the relationship (`accessing_from`) or are otherwise open to the caller.\", \"base64\": false}]}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"3.37.1\", \"versionStartIncluding\": \"3.24.0\"}], \"operator\": \"OR\"}], \"operator\": \"AND\"}], \"providerMetadata\": {\"orgId\": \"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\", \"shortName\": \"EEF\", \"dateUpdated\": \"2026-10-25T19:47:30.612Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2026-114214\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-10-26T14:35:21.414Z\", \"dateReserved\": \"2026-10-25T14:30:01.870Z\", \"assignerOrgId\": \"6b3ad84c-e1a6-4bf7-a703-f496b71e49db\", \"datePublished\": \"2026-10-25T19:47:30.612Z\", \"assignerShortName\": \"EEF\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…