fix: remediate AgentEx Trivy findings

[scale-ballen]

Summary

• bump agentex-ui Next.js to 15.5.18
• bump urllib3 to 2.7.0 in the uv lockfile
• add a langchain-core >=1.3.3 override and refresh uv.lock

Verification

• npm run build
• npm run typecheck
• uv export --frozen --no-dev --package agentex-backend --no-emit-package agentex-backend
• trivy fs --scanners vuln --severity HIGH,CRITICAL --pkg-types library --skip-dirs .venv --skip-dirs agentex-ui/node_modules --skip-dirs agentex-ui/.next --exit-code 1 .

Greptile Summary

This PR remediation bumps three vulnerable dependencies: Next.js 15.5.15 → 15.5.18 (frontend), urllib3 2.6.3 → 2.7.0 (Python), and langchain-core 1.2.22 → 1.3.3 (Python, via a new override-dependencies entry in pyproject.toml). The lockfile changes are minimal, internally consistent, and all package hashes are present. The langchain-core upgrade pulls in one new transitive dependency (langchain-protocol 0.0.15) which only depends on typing-extensions.

Confidence Score: 5/5

Safe to merge — purely dependency version bumps with no application logic changes.

All four files contain only dependency version updates. Lockfile hashes are consistent, package-lock.json is fully aligned, and the only new transitive dependency (langchain-protocol) is a minimal shim. No custom rules are violated.

No files require special attention.

Important Files Changed

Filename	Overview
pyproject.toml	Adds langchain-core>=1.3.3 override to force a patched version; straightforward and consistent with existing override pattern.
uv.lock	Bumps langchain-core 1.2.22 → 1.3.3 and urllib3 2.6.3 → 2.7.0; introduces one new transitive dep (langchain-protocol 0.0.15). All hashes present and consistent.
agentex-ui/package.json	Pins next to 15.5.18 (up from 15.5.15) to address CVE findings.
agentex-ui/package-lock.json	All ten Next.js package entries consistently updated to 15.5.18; diff is small and well-scoped.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Trivy Scan - HIGH/CRITICAL CVEs] --> B{Affected Components}
    B --> C[Next.js - Frontend]
    B --> D[urllib3 - Python HTTP]
    B --> E[langchain-core - Python AI]

    C --> C1[15.5.15 → 15.5.18\npackage.json + package-lock.json]
    D --> D1[2.6.3 → 2.7.0\nuv.lock]
    E --> E1[1.2.22 → 1.3.3\npyproject.toml override + uv.lock]
    E1 --> E2[New transitive dep:\nlangchain-protocol 0.0.15]

    C1 --> F[Trivy Scan Clean]
    D1 --> F
    E2 --> F

Loading

_{Reviews (1): Last reviewed commit: "fix: remediate agentex trivy findings" | Re-trigger Greptile}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​next@​15.5.15 ⏵ 15.5.18		+70	+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Potential vulnerability: npm next with risk level "medium" Location: Package overview From: agentex-ui/package-lock.json → npm/next@15.5.18 ℹ Read more on: This package | This alert | Navigating potential vulnerabilities Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: It is advisable to proceed with caution. Engage in a review of the package's security aspects and consider reaching out to the package maintainer for the latest information or patches. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/next@15.5.18. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report