#gitea — Public Fediverse posts

CISA warnt vor Angriffen auf diverse Software | Security https://www.heise.de/news/CISA-warnt-vor-Angriffen-auf-diverse-Software-11427406.html #exploit #Patchday #Gitea #MSSQL #Linux :tux:

Gitea Authors released #Gitea version 1.27.3. https://gitea.io/

Over 8,300 #Gitea servers vulnerable to code execution attacks

https://www.bleepingcomputer.com/news/security/over-8-300-gitea-servers-vulnerable-to-code-execution-attacks/

#cybersecurity #FOSS #DevOps

Gitea Servers Exposed to Ongoing Code Execution Attacks

Thousands of Gitea servers remain vulnerable to code execution attacks, with 8393 Internet-exposed IPs still susceptible to CVE-2026-60004, a code injection bug that lets attackers execute arbitrary shell commands. This flaw can be easily exploited by anyone with write access to a repository, which is especially concerning since Gitea enables…

https://osintsights.com/gitea-servers-exposed-to-ongoing-code-execution-attacks?utm_source=mastodon&utm_medium=social

#Cve202660004 #CodeExecution #Gitea #SupplyChain #EmergingThreats

"Building a Git comment system for Hugo"

I dropped WordPress from two of my sites, moving comments on one to Mastodon and building a custom, databaseless Go/Docker API for the other that submits comments as YAML files via Pull Requests for build-time rendering...

🔗 https://ricard.dev/building-a-git-comment-system-for-hugo/

#Hugo #Docker #Gitea

Hackers now exploit critical #Gitea flaw in code injection attacks

https://www.bleepingcomputer.com/news/security/hackers-now-exploit-critical-gitea-flaw-in-code-injection-attacks/

#cybersecurity #FOSS

Status Report 2026-08-29 and Outlook for September\October 2026

Today we released Infinito.Nexus 13.0.0 with integrated Tor and .onion support. The release notes you will find here and the blog article about the functionality here.

https://www.youtube.com/watch?v=6czcc1gZ7Ak

This feature didn’t have a high business value, anyhow it allowed to clean up the architectural base for everything what comes now.

Anyhow here I want to give you insights into the Infinito.Nexus project and what’s planed.

Infinito.Nexus Core >= 14.0.0a

Email Software Replacement

From the current point of view at least 2 Major releases will arrive in the next month. The first one is the substitution of Mailu by Stalwart, implemented by Alejandro. This is necessary due to the deprecation of Mailu itself.

https://www.youtube.com/watch?v=lJqtQG6lmc4&t=24s

The release state and the related discussion you can follow here .

AI Integration

The other release is, let’s call it the “AI” release. Long story short:
Infinito.Nexus will allow the use and the integration of AI, local and external models in almost all SaaS applications. It will also allow the Integration in Software via MCP.

Lite LLM

All applications which support AI like OpenWebUI, WordPress, Nextcloud, Matrix etc. will have an inteface which connects to an Lite LLM Gateway. The Lite LLM Gateway will allow the use of local models like Qwen, Gema etc. Besides this it’s possible to integrate OpenRouter or e.g. Anthropic or OpenAI etc.

https://www.youtube.com/watch?v=nQCOTzS5oU0

So enterprises which use Infinito.Nexus can decide by themself if they prefer to use their local AI and models and keep everything on their infrastructure or if they prefer to use external proprietary models.

The customer has the choice about the level of data sovereignty they want to keep and the infrastructure which they want to setup.

MCP

https://youtu.be/eur8dUO9mvE?si=vTJW30tCZz2ZdUD6

The second AI related topic is the integration of MCP into all kind of applications.

It’s already in progress since a few weeks and my agents are working on this 24h. Relevant in this context is the security aspect.

Similar to the Infinito.Nexus 13.0.0 TOR Release, the MCP Release will have a high impact on security and MUST due to this reason be declared as PoC. Why?

In my understanding you can’t easily implement RBAC into MCP clients.
So my current implementation works like this;

You have per Infinito.Nexus application two MCP RBAC groups:

• Reader
• Writer

If one is part of the reader group they can read all of the application data via Open WebUI and if one is part of the Writer group they can modify all of the data via Open WebUI.

https://www.youtube.com/watch?v=VNPMl8oOzHU

This is off course highly dangerous. It may makes sense to give people reading rights, but in consequence this means that they can access and utilize all of the users data via an AI.

We don’t have to talk about that this goes against any kind of data protection regulations and is a hard invasion into the privacy of your platform users.

Anyhow there are scenarios in which it may makes sense.

E.g. let’s assume you’re fully virtual organisation and you don’t have humans employed, but instead on your Infinito.Nexus platform just bot and agents account exist;

In this scenario if you have reading and writing rights you’re de facto in the “God Mode” in which you can instantly see what your agents are doing.

An example is if you use it e.g. with AgentCrew (WiP). You can orchestrate Agents and AI on a way you can’t imagine. AgentCrew I will explain in the next paragraphs.

Also if it’s in the current state absolutely not recommended to activate the MCP functionality, it doesn’t mean it must be like this in the future. Like I said currently it’s seen as PoC and the full MCP compatible RBAC implementation isn’t impossible, it just will take a lot of human resources, because for every part of the Infinito.Nexus software we need humans which take responsibility for the code.

“We stay in the loop” – We aren’t controlled by AI, instead we’re the masters. In consequenz this means that the full RBAC MCP will be implemented as soon as we have sufficient customers which request it and developers which can manage it intellectually to implement a clean architectural solution.

i18n

Besides the AI topic there is one key thing missing in the Infinito.Nexus Core Repository, but also in the Store and this is the implementation of the 184 ISO 639-1 into our software solution.

The software was primarily designed with German customers and the debate about digital sovereignty of European and especially German enterprises from American Big Tech in mind. Still some frontend elements like the dashboard just supported English as language.

The implementation of German is off course an hard requirement before it can be distributed and promoted on the DACH market. Actually I figured out that there is a easy design pattern to implement this, so part of the 14/15th major release will also be the support of all 184 ISO 639-1 languages.

Infinito.Nexus Store

Besides the Core development the AI Agents of course worked in the last weeks on implementing the store.

Theoretically the store is ready. Off course there are a few issues but overall I think it’s heading in the right direction.

Somewhere in the next weeks I will release a beta version of the store, but before we use it in production there needs to be a deeper security audit.

The store itself is from my point of view at the current situation the weakest part in the security chain and could be used by attackers as entry point into our system. So I don’t feel confident yet to release it, but I have some ideas in my mind how I can use AI supported attacks against the store to penetrate the system and to find all loopholes.

Besides this the API’s for auto-provisioning of enterprise infrastructure are currently just implemented as mocks.

The reason therefore is again a resource issue on my side. To implement them, do the billing etc. I need people in the back office which take care about the bureaucracy and right now we’re just a bunch of programmers.

So the bottleneck since the start of this project is still to have people in the back office, administration and on the business side which could take over tasks like this. Currently we don’t have anybody for this tasks.

Agentic Projects

Besides Core and Store there are two other IT projects which I want to mention.

AgentBox

The first one is AgentBox. The idea behind AgentBox is to encapsulate the agents which work on your code in an highly isolated environment.

This is necessary due to the reason that the agents are currently working in sandboxes like the one which Claude ships onboard, but they can easily break out. It’s just a question of will.

If the agent decides that they want to break out they can break out and can take control over your system. Due to this reason I’m working on a better cage to keep them isolated. I first will use this as part of the Store aka. GUI repo and as soon as I feel confident I will also “box” all of my other repos.

It will be part of PKGMGR so that I can setup and develop new solutions much faster and much safer then ever before.

AgentCrew

The second one is AgentCrew. AgentCrew addresses the problem, that this project requires a lot of people to run and set up a business.

A few weeks ago, during a chat with Amadeus, we talked about that there are existing frameworks like ITIL, SAFe, etc. which describe in detail how to set up an Enterprise Organisation.

With AgentCrew you decide for a framework, define framework roles, characters and the related LLM to use. All people which are normally human beings are replaced by an agent and they will take over the roles.

Due to the reason that not all of the roles need the same capabilities it’s possible to give some agents lower models and other agents better models. In kombination with OpenRouter and local LLM’s you can scale up an organisation for very low costs.

The advantage for us as Infinito.Nexus team is, that we developed the infrastructure tool to give every agent their own account with all tools which they need. Let it be developing tools like gitea\GitLab\jenkins, project management tools like Taiga\OpenProject, cloud access via Nextcloud etc.

Infinito.Nexus can be the base to setup fully autonom working agentic teams.

I will focus on AgentCrew as soon as the store is ready, because then we need urgently agents in the back office, distribution etc.

Business Strategy

The strategy stays the following; The focus is on finishing the core like mentioned above.

Parallel the development of the store continous.

As soon as the store is ready I will contact all people in our CRM system.

Besides this is would be good to get some low level investment. We have now a ready product. A little money as an catalyst to enlighten the engine for digital sovereignty would make our life much easier, but it will also work without it.

The advantage which we have is that as soon as the store is standing and the API’s are integrated we have an scalable product with almost non fix costs, so we can beat all of our competitors by price.

Besides this it’s almost impossible that a real competitor raises.

And now you ask me the question:

Why? Kevin hadn’t you been an hypocrat? Didn’t you tough in your position as agile coach that you find customers and develop a project dependent on their needs and scale up your business by realizing what your customer needs from you?

I can tell you it would had been impossible.

If we would have customers already, we couldn’t had developed an clean architectural solution. We would had acquired a huge amount of technical debt due to the reason that we would had been required to maintain outdated infrastructure and couldn’t implement the radical architectural design which was necessary to implement a tool which can compete in the times of AI with the other companies.

A lot of businesses will fail in the next month and years. The reason therefore is that they vibe coded bad software which is unmaintainable. Our solution is as well designed as as Rolex and usable like a Swiss Pocket Knife.

I don’t know any other software company which delivers such an high quality like we’re doing and we can dump the price almost as low as we like.

Vibe Coding and Agentic Engineering

https://www.youtube.com/watch?v=PbsocBPkoUc

One last sentence I would like to mention concerning vibe coding and agentic engineering and how I apply both practices. So you have an idea how I could realize such an project.

I would say in general I use classical software engineering practices.

• Writing well defined requirements documents\ADR witch AC
• Writing test for them
• Let the AI iterate against the tests until all of them pass

The AI works in general autonomously. I inspect the code before commiting and steer the AI in the right direction.

With a lot of the implementations I don’t have any glue at the beginning of the feature how to realize this exactly. This counts e.g. for the docker swarm implementation, the tor implementation, but also the current MCP implementation.

So I let the AI turn wild but I question critically the output and the modifications. The most of the time I have at least 3 agents parallel running which are working on different topics.

Still I need to review all of the code and I feel responsible to understand what the agents are doing. I have the final say about the best approach.

This means that in the last month I still had my 16 hour days just reviewing, deciding and understanding what’s going on, besides that the AI is working parallel 24/7.

I really look forward to the point when this isn’t my daily business anymore.

I hope anybody who is interested in it has now a betting understanding where the project stands, what final challenges have to be tackled and where we will stand in approx. 2 month.

Gitea Flaw Exploited in Code Injection Attacks

A critical flaw in Gitea, tracked as CVE-2026-60004, is being actively exploited in code injection attacks, putting nearly 5,000 self-hosted Git service instances at risk. Attackers can inject malicious code by submitting patches via Gitea's diffpatch API endpoint, allowing them to execute arbitrary shell commands.

https://osintsights.com/gitea-flaw-exploited-in-code-injection-attacks?utm_source=mastodon&utm_medium=social

#Gitea #CodeInjection #Cve202660004 #SupplyChain #EmergingThreats

Gitea Flaw Exploited to Deploy Miner-Like Payload

Hackers are actively exploiting a critical flaw in Gitea to deploy malicious payloads, including miner-like attacks, by abusing the diffpatch endpoint to install and execute Git hooks. This vulnerability allows attackers with repository write access to inject code and run shell commands, prompting a warning from the US Cybersecurity and…

https://osintsights.com/gitea-flaw-exploited-to-deploy-miner-like-payload?utm_source=mastodon&utm_medium=social

#Gitea #CodeInjection #SupplyChain #KnownExploitedVulnerabilities #Cisa

So #indieweb, right? https://www.yevi.org/ is already a static site in #HTML and #CSS written by hands (my hands). It’s time to fix the deployment process of it because now I’m packing it into a #Docker image with #nginx. So each of my websites is a Docker container with its own Nginx, which is definitely overkill for #indieweb.

I want a single Nginx with several sites. What are my options for automated deployments from #Gitea? #Ansible? Simple scp? I think scp is a nice option.

Maiao: Gerrit-style code review workflow for GitHub, GitLab, Gitea, others

https://github.com/runetes/maiao

Comments: https://news.ycombinator.com/item?id=49441666

#HackerNews #Maiao #Gerrit #Code #Review #GitHub #GitLab #Gitea

Von GitHub wegkommen? Gar nicht so einfach!

Der letzte GitHub-Ausfall, war der Tropfen, der das Fass zum Überlaufen gebracht hat. Aber hey, es ist gar nicht so einfach, davon wegzukommen.

zum Blogpost…

#blogpost #blog #GitHub #Downtimes #Gitea #Actions #GoProxy #Golang #NPM #Dependencies #Self-Hosting

Hey @worktree @alexblackie possibly dumb question, but I couldn't find it in the UI; how do I get Worktree to email me when someone makes an Issue in one of my repos? 🤔

#Worktree #Gitea

#Gitea runner 3.3.0 is out

🔗 https://gitea.com/gitea/runner/releases/tag/v3.3.0

My #Gitea instance started acting up a few days ago, I was worried it was going to be some obscure issue. When I took some time to dig in turns out the #PostgreSQL server had shut itself down cleanly and didn't restart probably during a package update. Restarted the server and added Restart=always to the #systemd service file so hopefully it won't happen again 😅

Good thing the only one who cares about uptime is me.

#selfhosting #Linux #git #Debian

Криптомайнер на Gitea: 70% нагрузки CPU, RCE в self-hosted Gitea вместо GitLab и как я закрыл уязвимость

Всё началось с обычного письма от хостинга: VPS слишком долго держит CPU выше 70%. Я открыл Gitea посмотреть, что происходит, а там уже был чужой репозиторий. По логам восстановил атаку почти по секундам: регистрация, repository, diffpatch, Git hook, RCE. От первого запроса до proof прошло около 11 секунд. А дальше обнаружился loader крипто-майнера. Покажу, как это произошло и что пришлось переделать на сервере. Читать разбор

https://habr.com/ru/articles/1072030/

#Gitea #GitLab #selfhosted_Gitea #RCE #CVE202660004 #Gitрепозитории #Docker #криптомайнер #информационная_безопасность #incident_response

"Moving away from GitHub to self hosted Gitea"

For years, I was a heavy GitHub user with around 100 repositories, using it simply for static file hosting, GitHub Pages, and basic CI/CD workflows like Hugo or custom Node builds...

🔗 https://ricard.dev//moving-away-from-github-to-self-hosted-gitea//

#Linux #Gitea #GitHub #Docker

✅️ Migrated another #WordPress site to #Hugo.

1️⃣ I only post photos with no text, so it was cumbersome to create single WordPress posts for each photo.

2️⃣ Hugo has a way to loop through a directory, so now I simply loop through a folder with 2000 photos and print <img> with loading lazy.

😨 My self-hosted #Gitea instance had a moment of panic as it couldn't handle a commit with 700 Mb in assets. But it's all good now.

🤖 I've also added #Anubis in front.

🔗 https://ricard.photos

@navi well well well, it's time to self host a #Gitea instance. With #Docker it's a matter of minutes to be up and running.

You get 1 of the 2 problems solved 😎

@pawelgrzybek Time to self host a #Gitea instance?

I did the move a few weeks ago and I'm very happy with the result.

#Github

Gitea Authors released #Gitea version 1.27.2. https://gitea.io/

While most of the OSS world and hobbiest seemed to move from #Gitea to #forgejo, I went into the another direction and installed #Gogs as it fits my needs.

It was also the only one that actually compiled on my #OpenBSD install. 🤫

Thanks to @OpenBSDAms for hosting this little box. 😍

Gitea: 55 CVEs, avg CVSS 6.74, max 9.9. 92% unpatched. Trust Score: C. Open-source Git service, but top flaws CWE-284/863/862. Patch or risk repo compromise. #Gitea #infosec #cybersecurity

https://www.valtersit.com/vendors/gitea/

Remember when I said my DR setup should have me back up in 20-30 minutes? Yeah. About that. Turns out a backup job can run clean every single night for months and still not actually be backing up what you think it is. So here's what I actually found out the hard way replacing nixos2's dying hardware. Feel free to cue the old "The more you know" clip.

https://blog.ppb1701.com/best-laid-plans-replacing-nixos2s-failing-hardware-part-19-of-building-a-resilient-home-server-serie

#blog #homeserver #nixos #disasterrecovery #selfhosting #gitea #tailscale