1sealsemantic last-mile verification

Research / Finding

Network policy agent: return errors from eBPF map updates

F-NPA-FAILOPEN-001

Public snapshot: 7 Oct 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Read the evidence · View in research browse

Recorded evidence

—score not recorded
aws/aws-network-policy-agentReported fixaws/aws-network-policy-agent

Network policy agent: return errors from eBPF map updates

Fixed in: AWS network policy agent v1.3.7 contains PR #562

fixed publicly
details
Finding IDs
F-NPA-FAILOPEN-001
Status
fixed publicly
Fixed in
AWS network policy agent v1.3.7 contains PR #562
Recorded credit
Public fix author: parlakisik. Public 1seal credit and a causal link to our report are not established.
Note
Merged 2026-05-21. The patch returns joined errors from policy and pod-state map updates instead of hiding failed writes and adds caller-facing regression tests. This matches the reported error-propagation defect and is separate from PR #563. The earlier reduced model did not demonstrate traffic blocking after a failure. Complete network protection after partial update failure is not established by this record; no separate CVE is assigned.

F-NPA-FAILOPEN-001: Input / state handling. A failed policy-map update must return an error so its caller does not treat incomplete enforcement as success. Reviewed 7 Oct 2026. Mechanism assessed by 1seal.

Mechanism source for F-NPA-FAILOPEN-001

Security area (1seal assessment): Authorization. A failed policy-map update must return an error so its caller does not treat incomplete enforcement as success. Reviewed 7 Oct 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.