NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data.
NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Sep 1, 2026
- Updated
- Sep 2, 2026
- EPSS
- 0.4% · 32th percentile
- CWE
- CWE-502
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · nvidia
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| nvidia | nemo megatron bridge | cpe:2.3:a:nvidia:nemo_megatron_bridge |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nvidia nemo megatron bridgebefore 0.5.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (nvidia). Independent of NVD's CPE analysis and usually ahead of it.
NVIDIA Megatron Bridge
- 0.0 to 0.5.0affected
Same product
nvidia: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-61779NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data.31Monitor
- CVE-2026-61778NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data.31Monitor
- CVE-2026-61776NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data.31Monitor
- CVE-2026-61775NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data.31Monitor
- CVE-2026-61774NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data.31Monitor
- CVE-2026-61773NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data.31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-617570 days apartNVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data.31Monitor
- CVE-2026-617620 days apartNVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data.31Monitor
- CVE-2026-617630 days apartNVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data.31Monitor
- CVE-2026-617640 days apartNVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data.31Monitor
- CVE-2026-617650 days apartNVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data.31Monitor
- CVE-2026-617660 days apartNVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data.31Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
- NVIDIA Public Bug BountyIntigriti · paid · up to $15,000
- NVIDIA Vulnerability Disclosure ProgramIntigriti · disclosure only (VDP)
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-502 · Deserialization of Untrusted DataCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.
The bug in code
The whole CWE-502 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
payload = sock.recv(65536)job = pickle.loads(payload)Fixed
payload = sock.recv(65536)if not hmac.compare_digest(sign(payload), header_sig): raise PermissionError("invalid signature")job = JobSchema.validate(json.loads(payload))Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- github.com/NVIDIA/product-security/tree/main/2026/5868
- nvd.nist.gov/vuln/detail/CVE-2026-61777
- www.cve.org/CVERecord?id=CVE-2026-61777
Vendor advisories and official records. Exploit/PoC links are deliberately left out.