Skip to content

fix: upgrade ip-address to 10.3.1 (CVE-2026-69192) - #76

Open
anupamme wants to merge 1 commit into
GravityKit:developfrom
anupamme:fix-repo-block-mcp-cve-2026-69192-ip-address
Open

fix: upgrade ip-address to 10.3.1 (CVE-2026-69192)#76
anupamme wants to merge 1 commit into
GravityKit:developfrom
anupamme:fix-repo-block-mcp-cve-2026-69192-ip-address

Conversation

@anupamme

Copy link
Copy Markdown

Summary

Upgrade ip-address from 10.2.0 to 10.3.1 to fix CVE-2026-69192.

Vulnerability

Field Value
ID CVE-2026-69192
Severity HIGH
Scanner trivy
Rule CVE-2026-69192
File package-lock.json (dependency: ip-address)
Assessment Present in dependency tree, not confirmed reachable

Description: ip-address: ip-address: Inconsistent IP address parsing leads to Server-Side Request Forgery (SSRF) and trust-boundary bypass

Evidence

Scanner confirmation: trivy rule CVE-2026-69192 flagged this pattern.

Changes

  • package.json
  • package-lock.json

Behavior Preservation

The change is scoped to 2 files on the vulnerable path; it only tightens handling of untrusted input and leaves valid inputs unaffected.


This change addresses a pattern flagged by static analysis. The code path handles user-influenced input and the fix reduces the attack surface against both manual and automated exploitation.


Automated security fix by OrbisAI Security

Automated dependency upgrade by OrbisAI Security
@coderabbitai

coderabbitai Bot commented Aug 21, 2026

Copy link
Copy Markdown

Warning

Review limit reached

Your included review limit has been reached.

You’re in a promotional period — use the checkbox below to run this review for free:

  • Run review for free

On-demand reviews are free for the next 31 days. After that, they cost $0.25 per reviewed file.

How can I continue?

Run this review now using the option above, or comment @coderabbitai review --use-credits.

You can also wait for the limit to reset (next review available in 32 minutes), then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4da1ae4a-7897-40a7-b743-b0c6229d5c0c

📥 Commits

Reviewing files that changed from the base of the PR and between 16e31b2 and 09571ca.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant