{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-63310", "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10", "state": "REJECTED", "assignerShortName": "VulnCheck", "dateReserved": "2026-07-16T12:13:18.733Z", "datePublished": "2026-08-22T14:12:39.360Z", "dateUpdated": "2026-09-14T23:10:03.270Z", "dateRejected": "2026-09-14T23:10:03.270Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10", "shortName": "VulnCheck", "dateUpdated": "2026-09-14T23:10:03.270Z"}, "rejectedReasons": [{"lang": "en", "value": "This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.", "supportingMedia": [{"type": "text/html", "base64": false, "value": "This CVE ID has been rejected or withdrawn by its CVE Numbering Authority."}]}], "x_generator": {"engine": "Vulnogram 1.0.5"}}}}

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-63310", "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10", "state": "REJECTED", "assignerShortName": "VulnCheck", "dateReserved": "2026-07-16T12:13:18.733Z", "datePublished": "2026-08-22T14:12:39.360Z", "dateUpdated": "2026-09-14T23:10:03.270Z", "dateRejected": "2026-09-14T23:10:03.270Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10", "shortName": "VulnCheck", "dateUpdated": "2026-09-14T23:10:03.270Z"}, "rejectedReasons": [{"lang": "en", "value": "This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.", "supportingMedia": [{"type": "text/html", "base64": false, "value": "This CVE ID has been rejected or withdrawn by its CVE Numbering Authority."}]}], "x_generator": {"engine": "Vulnogram 1.0.5"}}}}

{"cveTags": [], "descriptions": [{"lang": "en", "value": "Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority."}], "id": "CVE-2026-63310", "lastModified": "2026-09-15T00:16:57.827", "metrics": {}, "published": "2026-08-22T15:16:19.100", "references": [], "sourceIdentifier": "disclosure@vulncheck.com", "vulnStatus": "Rejected"}

{"bugzilla": {"description": "nltk: NLTK before 3.9.3 Missing Post-Download Integrity Verification", "id": "2521337", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2521337"}, "csaw": false, "cvss3": {"cvss3_base_score": "7.1", "cvss3_scoring_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:H", "status": "draft"}, "cwe": "CWE-494", "details": ["NLTK before 3.9.3 fails to verify file integrity after downloading packages and before extraction in the downloader module. Attackers can perform man-in-the-middle attacks or DNS poisoning to inject malicious package contents that are extracted without validation.", "NLTK before 3.9.3 fails to verify file integrity after downloading packages and before extraction in the downloader module. Attackers can perform man-in-the-middle attacks or DNS poisoning to inject malicious package contents that are extracted without validation."], "mitigation": {"lang": "en:us", "value": "Upgrade the nltk package to version 3.9.3 or later, which adds post-download integrity verification before extraction. Pin this minimum version in requirements files, lockfiles, and container image builds for all affected components.\nWhere an immediate upgrade is not possible: avoid invoking NLTK's automatic downloader over untrusted or unauthenticated networks. Pre-download and independently verify the required NLTK data packages from a trusted source, host them in an internal, integrity-checked artifact repository, and point NLTK_DATA at that vetted local store so the runtime process never fetches data over the wire. Enforcing TLS with certificate validation and using trusted, DNSSEC-validated resolvers for the download endpoint reduces exposure to MITM/DNS-poisoning attacks but does not substitute for upgrading, since the underlying missing-integrity-check flaw remains present."}, "name": "CVE-2026-63310", "package_state": [{"cpe": "cpe:/a:redhat:exploit_intelligence:0", "fix_state": "Under investigation", "package_name": "exploit-intelligence-tech-preview/vulnerability-analysis-rhel9", "product_name": "Exploit Intelligence"}, {"cpe": "cpe:/a:redhat:lightspeed_core", "fix_state": "Not affected", "package_name": "lightspeed-core/lightspeed-stack-rhel9", "product_name": "Lightspeed Core"}, {"cpe": "cpe:/a:redhat:lightspeed_core", "fix_state": "Not affected", "package_name": "lightspeed-core/rag-tool-cpu-rhel9", "product_name": "Lightspeed Core"}, {"cpe": "cpe:/a:redhat:lightspeed_core", "fix_state": "Not affected", "package_name": "lightspeed-core/rag-tool-cuda-12.9-rhel9", "product_name": "Lightspeed Core"}, {"cpe": "cpe:/a:redhat:openshift_lightspeed", "fix_state": "Not affected", "package_name": "openshift-lightspeed/lightspeed-ocp-rag-rhel9", "product_name": "OpenShift Lightspeed"}, {"cpe": "cpe:/a:redhat:openshift_lightspeed", "fix_state": "Not affected", "package_name": "openshift-lightspeed/lightspeed-service-api-rhel9", "product_name": "OpenShift Lightspeed"}, {"cpe": "cpe:/a:redhat:openshift_lightspeed", "fix_state": "Not affected", "package_name": "openshift-lightspeed-tech-preview/lightspeed-rag-tool-rhel9", "product_name": "OpenShift Lightspeed"}, {"cpe": "cpe:/a:redhat:ansible_automation_platform:2", "fix_state": "Affected", "package_name": "ansible-automation-platform-25/lightspeed-chatbot-rhel8", "product_name": "Red Hat Ansible Automation Platform 2"}, {"cpe": "cpe:/a:redhat:openshift_ai", "fix_state": "Under investigation", "package_name": "rhoai/odh-llama-stack-core-rhel9", "product_name": "Red Hat OpenShift AI (RHOAI)"}, {"cpe": "cpe:/a:redhat:openshift_ai", "fix_state": "Not affected", "package_name": "rhoai/odh-ogx-core-rhel9", "product_name": "Red Hat OpenShift AI (RHOAI)"}, {"cpe": "cpe:/a:redhat:openshift_ai", "fix_state": "Not affected", "package_name": "rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9", "product_name": "Red Hat OpenShift AI (RHOAI)"}, {"cpe": "cpe:/a:redhat:openshift_ai", "fix_state": "Under investigation", "package_name": "rhoai/odh-ta-lmes-job-rhel9", "product_name": "Red Hat OpenShift AI (RHOAI)"}, {"cpe": "cpe:/a:redhat:openshift_ai", "fix_state": "Not affected", "package_name": "rhoai/odh-trustyai-garak-lls-provider-dsp-rhel9", "product_name": "Red Hat OpenShift AI (RHOAI)"}, {"cpe": "cpe:/a:redhat:openshift_ai", "fix_state": "Under investigation", "package_name": "rhoai/odh-trustyai-nemo-guardrails-server-rhel9", "product_name": "Red Hat OpenShift AI (RHOAI)"}, {"cpe": "cpe:/a:redhat:openshift_ai", "fix_state": "Not affected", "package_name": "rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9", "product_name": "Red Hat OpenShift AI (RHOAI)"}], "public_date": "2026-08-22T14:12:39Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-63310\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-63310\nhttps://github.com/nltk/nltk/security/advisories/GHSA-5wp5-5229-5g6q\nhttps://www.vulncheck.com/advisories/nltk-before-missing-post-download-integrity-verification"], "statement": "Red Hat has rated this issue as having an Impact of Important. This flaw is only exploitable when application code calls NLTK's downloader module (e.g. nltk.download()) to fetch corpora or model packages from the network at runtime, and an attacker is able to intercept or redirect that traffic via a man-in-the-middle position or DNS poisoning. Red Hat products that vendor nltk but do not invoke the downloader at runtime -- for example, images that ship pre-bundled NLTK data baked in at build time -- are not affected by this flaw regardless of the packaged nltk version.", "threat_severity": "Important"}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[0,3.9.3)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "3.9.3"}}], "enrichment": {"confidence": 95.0, "confidence_source": "inferred", "scores": [{"score": 95.0, "source": "inferred"}, {"score": 100.0, "source": "matching"}]}, "original": {"product": "nltk", "source": "cna", "vendor": "nltk"}, "product": "nltk", "vendor": "nltk"}], "created": "2026-08-22T15:30:05.816041+00:00", "updated": "2026-08-22T16:00:12.985976+00:00", "vendors": ["nltk", "nltk$PRODUCT$nltk"]}